#18752: libiconv fails to build because configure.cc not set --------------------------------------+------------------------------------- Reporter: dale+macports@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: | Port: libiconv --------------------------------------+------------------------------------- Comment(by dale+macports@…): Replying to [comment:2 mcalhoun@...]:
By chance, are you running an older version of MacPorts?
I don't think so? {{{ $ port version Version: 1.700 $ uname -a Darwin dale 9.6.0 Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386 i386 }}} And I've done `port -d selfupdate` several times today. However I totally buy your explanation that something is up, because I've got `port upgrade outdated` running and a ton of ports are failing like this: {{{ ---> Building py25-zlib with target build Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_python_py25-zlib/work/Python-2.5.4/Modules" && /opt/local/bin/python2.5 setup.py build " returned error 1 Command output: running build running build_ext building 'zlib' extension -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I/opt/local/include -I/opt/local/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5 -c zlibmodule.c -o build/temp.macosx-10.3-i386-2.5/zlibmodule.o unable to execute -DNDEBUG: No such file or directory error: command '-DNDEBUG' failed with exit status 1 }}} This smells to me like my compiler isn't getting defined in the right place somehow, and not a problem with the libiconv port. If someone knowledgeable concurs with this statement, please feel free to close this ticket as invalid. -- Ticket URL: <http://trac.macports.org/ticket/18752#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS