[MacPorts] #15061: Multiple python build errors ("unable to
execute -DNDEBUG: No such file or directory")
MacPorts
trac at macosforge.org
Sun Apr 20 03:21:29 PDT 2008
#15061: Multiple python build errors ("unable to execute -DNDEBUG: No such file or
directory")
-------------------------------+--------------------------------------------
Reporter: akfaka at yahoo.com | Owner: macports-tickets at lists.macosforge.org
Type: defect | Status: new
Priority: High | Milestone: Port Bugs
Component: ports | Version: 1.6.0
Resolution: | Keywords:
-------------------------------+--------------------------------------------
Comment (by akfaka at yahoo.com):
Ok, I suspected it is a issue with python, so I went to their site,
downloaded and installed from Universal MacPython 2.5.2.dmg
Then I did port install wireshark again, this time I didn't get the python
related error, BUT now there is something with the gtk,
...
Error: Target org.macports.configure returned: configure failure: shell
command " cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports
.org_release_ports_gnome_gtk-doc/work/gtk-doc-1.10" && ./configure
--prefix=/opt/local --with-xml-catalog=/opt/local/etc/xml/catalog "
returned error 1
Command output: configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by /usr/bin/g++-4.0... /usr/libexec/gcc/i686-apple-
darwin9/4.0.1/ld
checking if the linker (/usr/libexec/gcc/i686-apple-darwin9/4.0.1/ld) is
GNU ld... no
checking whether the /usr/bin/g++-4.0 linker (/usr/libexec/gcc/i686-apple-
darwin9/4.0.1/ld) supports shared libraries... yes
checking for /usr/bin/g++-4.0 option to produce PIC... -fno-common
checking if /usr/bin/g++-4.0 PIC flag -fno-common works... yes
checking if /usr/bin/g++-4.0 static flag -static works... no
checking if /usr/bin/g++-4.0 supports -c -o file.o... yes
checking whether the /usr/bin/g++-4.0 linker (/usr/libexec/gcc/i686-apple-
darwin9/4.0.1/ld) supports shared libraries... yes
checking dynamic linker characteristics... darwin9.2.2 dyld
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
What do I do now? Can someone offer some help? I thought Macports is
supposed to make installation less pain but I started to feel like I am
working with Garbagesoft Windows machine again :0
--
Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/15061#comment:4>
MacPorts </projects/macports>
Ports system for Mac OS
More information about the macports-tickets
mailing list