"unable to execute -DNDEBUG" - strange gnucash build failure
Hello After a "sudo port install gnucash +without_docs" I got this, probably my favorite Christmas-bug, so far I haven't been able to reduplicate it (another run of "sudo port -d install gnucash +without_docs" gave me another error ... see next posting). It's completely obscure for me that the error message seems to be related to gdbm, a fair while after that port was activated. "-DNDEBUG" doesn't probably exist as a command, well, I thought so. "libdaemon" ("libdaemon @0.12_0 (active)"!) has got through its activation, too, though any feedback was missing ... see console messages below. Also weird: gdbm seems to be properly installed ... a "port installed" lists gdbm @1.8.3_1 (active), and I definitely don't need anything built for Panther (MacOS 10.3). 1 Mio. $ Question: What went wrong here? My environment looks basically like this: PowerPC, macport 1.6.0 (1x selfupdate yesterday) at /opt/local/, a new installation of Leopard, XCode 3 (from DVD, that's still the most recent version available at connect.apple.com). Cheers Peter ... ######################################################################### ---> Fetching gdbm ---> Attempting to fetch gdbm-1.8.3.tar.gz from http://ftp.gnu.org/gnu/gdbm ---> Verifying checksum(s) for gdbm ---> Extracting gdbm ---> Applying patches to gdbm ---> Configuring gdbm ---> Building gdbm with target all ---> Staging gdbm into destroot ---> Installing gdbm 1.8.3_1 ---> Activating gdbm 1.8.3_1 ---> Cleaning gdbm ---> Fetching libdaemon ---> Attempting to fetch libdaemon-0.12.tar.gz from http://0pointer.de/lennart/projects/libdaemon/ ---> Verifying checksum(s) for libdaemon ---> Extracting libdaemon ---> Configuring libdaemon ---> Building libdaemon with target all ---> Staging libdaemon into destroot ---> Installing libdaemon 0.12_0 running build_ext building 'gdbm' extension creating build creating build/temp.macosx-10.3-ppc-2.5 -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I/opt/local/include -I/opt/local/include/python2.5 -c gdbmmodule.c -o build/temp.macosx-10.3-ppc-2.5/gdbmmodule.o unable to execute -DNDEBUG: No such file or directory error: command '-DNDEBUG' failed with exit status 1 Error: The following dependencies failed to build: evince avahi py25-gdbm py25-gtk py25-cairo esound gconf intltool orbit2 libidl gnome-doc-utils iso-codes py25-hashlib openssl py25-libxml2 gnome-icon-theme icon-naming-utils p5-getopt-long p5-pathtools p5-xml-simple p5-test-simple p5-test-harness p5-xml-namespacesupport p5-xml-sax gnome-keyring libgcrypt libgpg-error gnome-vfs gnome-mime-data howl neon libart_lgpl libgnome libbonobo popt libgnomecanvas gail libgnomeui libbonoboui m4 nautilus eel gnome-desktop fribidi startup-notification gnome-menus libexif librsvg libcroco libgsf shared-mime-info poppler poppler-data goffice03 libgnomeprintui libgnomeprint bison libgnomecups pcre guile16 readline ncurses ncursesw gawk libgtkhtml3 p5-finance-quote p5-crypt-ssleay p5-libwww-perl p5-compress-zlib p5-compress-raw-zlib p5-io-compress-base p5-scalar-list-utils p5-io-compress-zlib p5-html-parser p5-html-tagset p5-uri p5-datemanip p5-html-tableextract slib slib-guile16 Error: Status 1 encountered during processing. __________________________________________________________ Sent from Yahoo! Mail - a smarter inbox http://uk.mail.yahoo.com
On 01Jan1970 00:00, Peter Schneider <petr.snyder@yahoo.co.uk> wrote: | After a "sudo port install gnucash +without_docs" I got this, probably | my favorite Christmas-bug, so far I haven't been able to reduplicate it | (another run of "sudo port -d install gnucash +without_docs" gave me | another error ... see next posting). | | It's completely obscure for me that the error message seems to be | related to gdbm, a fair while after that port was activated. "-DNDEBUG" | doesn't probably exist as a command, well, I thought so. "libdaemon" | ("libdaemon @0.12_0 (active)"!) has got through its activation, too, | though any feedback was missing ... see console messages below. [...snip...] | ---> Building libdaemon with target all | ---> Staging libdaemon into destroot | ---> Installing libdaemon 0.12_0 | running build_ext | building 'gdbm' extension | creating build | creating build/temp.macosx-10.3-ppc-2.5 | -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I/opt/local/include -I/opt/local/include/python2.5 -c gdbmmodule.c -o build/temp.macosx-10.3-ppc-2.5/gdbmmodule.o | unable to execute -DNDEBUG: No such file or directory | error: command '-DNDEBUG' failed with exit status 1 Did you ever figure this out? It's happening to me, too, so several packages, often in the build step. It looks like the compiler name is missing i.e. the command line should start with "gcc" or "cc". It seems to be related to the python install. "which python" was finding /usr/bin/python (the MacOSX python). I have now done this: cd /opt/local/bin ln -s python2.5 python and with /opt/local/bin at the start of my $PATH things are now working. Shouldn't the python packages "know" their preferred python? (/opt/local/bin/python2.4 or /opt/local/bin/python2.5)? Or shouldn't /opt/local/bin/python already be set up? Cheers, -- Cameron Simpson <cs@zip.com.au> DoD#743 http://www.cskk.ezoshosting.com/cs/ It's as if all of Scottish cuisine is based on a dare. - Saturday Night Live Squidliness is next to DoDliness. - Ancient Tibetan Proverb
On Mar 17, 2008, at 21:03, Cameron Simpson wrote:
It seems to be related to the python install. "which python" was finding /usr/bin/python (the MacOSX python). I have now done this:
cd /opt/local/bin ln -s python2.5 python
and with /opt/local/bin at the start of my $PATH things are now working.
Shouldn't the python packages "know" their preferred python? (/opt/local/bin/python2.4 or /opt/local/bin/python2.5)? Or shouldn't /opt/local/bin/python already be set up?
You don't need to manually link python2.5 to python. Use the python_select port instead.
On 18Mar2008 00:26, Ryan Schmidt <ryandesign@macports.org> wrote:
It seems to be related to the python install. "which python" was finding /usr/bin/python (the MacOSX python). I have now done this: cd /opt/local/bin ln -s python2.5 python
and with /opt/local/bin at the start of my $PATH things are now working.
Shouldn't the python packages "know" their preferred python? (/opt/local/bin/python2.4 or /opt/local/bin/python2.5)? Or shouldn't /opt/local/bin/python already be set up?
You don't need to manually link python2.5 to python. Use the python_select port instead.
Hmm, ok: ae003730:~ root# port search python_select python_select sysutils/python_select 0.1 Switch the default python interpreter ae003730:~ root# rm /opt/local/bin/python ae003730:~ root# port install python_select ---> Fetching python_select ---> Attempting to fetch select-0.1.tar.gz from http://svn.macports.org/repository/macports/users/mww/select/ ---> Verifying checksum(s) for python_select ---> Extracting python_select ---> Configuring python_select ---> Building python_select with target all ---> Staging python_select into destroot ---> Installing python_select 0.1_3+darwin_9 ---> Activating python_select 0.1_3+darwin_9 ---> Cleaning python_select ae003730:~ root# ls -ld /opt/local/bin/python lrwxr-xr-x 1 root admin 18 Mar 18 17:11 /opt/local/bin/python -> /usr/bin/python2.5 ae003730:~ root# which python2.5 /opt/local/bin/python2.5 ae003730:~ root# Surprised! [...] Ah: ae003730:~ root# python_select python25 Selecting version "python25" for python ae003730:~ root# ls -ld /opt/local/bin/python lrwxr-xr-x 1 root admin 24 Mar 18 17:15 /opt/local/bin/python -> /opt/local/bin/python2.5 Victory! Thanks. Did your -NDEBUG problem go away? Is python_select a macports thing or more general? The man page doesn't document the options (besides mentioning that they exist). How to fix that? Cheers, -- Cameron Simpson <cs@zip.com.au> DoD#743 http://www.cskk.ezoshosting.com/cs/ Standing on the faces of midgets, I can see for yards. - David N Stivers D0D#857 <stiv@stat.rice.edu>
On Mar 18, 2008, at 01:18, Cameron Simpson wrote:
On 18Mar2008 00:26, Ryan Schmidt wrote:
You don't need to manually link python2.5 to python. Use the python_select port instead.
[snip]
Is python_select a macports thing or more general? The man page doesn't document the options (besides mentioning that they exist). How to fix that?
python_select was created by MacPorts contributor Markus Weissman for the MacPorts project. Its source is in the MacPorts repository: http://svn.macports.org/repository/macports/users/mww/select/ You can send suggestions to Markus, or file tickets for them in our issue tracker, or look at the source and submit patches...
participants (3)
-
Cameron Simpson
-
Peter Schneider
-
Ryan Schmidt