Upgrading to py25-bsddb @2.5.2_1 fails (db46 related?)

[tyoshida@…]

I am having a problem with upgrading py25-bsddb @2.5.2_0 to @2.5.2_1.

I'm running Mac OS X 10.5.3 (MacBook Pro, Intel Core 2 Duo 2.4GHz, 4GB RAM) and I have Xcode 3.1 installed (iPhone SDK beta 7). At the very bottom of the log, you will see the following:

creating build/temp.macosx-10.3-i386-2.5
-DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/opt/local/include/db46 -I/opt/local/include/python2.5 -c _bsddb.c -o build/temp.macosx-10.3-i386-2.5/_bsddb.o
unable to execute -DNDEBUG: No such file or directory
error: command '-DNDEBUG' failed with exit status 1

Warning: the following items did not execute (for py25-bsddb): org.macports.destroot org.macports.build
DEBUG: Registry error: db46 not registered as installed.
    invoked from within
"registry_installed ${portname}"
    invoked from within
"$workername eval registry_installed \${portname}"
Error: Unable to upgrade port: 1

It says db45 not registered as installed, but when I ran port installed | grep db, I see that db46 is activated. But if you read the log file, you will note:

libtool: install: warning: remember to run `libtool --finish /opt/local/lib/db46'
Installing DB utilities: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_databases_db46/work/destroot/opt/local/bin ...
libtool: install: warning: `libdb-4.6.la' has not been installed in `/opt/local/lib/db46'
...

I am wondering if there are any issues with my db46 installation as well (it was installed when I tried to upgrade py25-bsddb).

[tyoshida@…]

A debug log of py25-bsddb upgrade

[tyoshida@…]

Regarding the warning: libdb-4.6.la' has not been installed in /opt/local/lib/db46', I see libdb-4.6.la in /opt/local/lib/db46. So I don't know why I get that warning.

[danielluke (Daniel J. Luke)]

The libtool warning is an artifact of how MacPorts handles installing the software.

It looks like you're seeing a MacPorts bug that has been fixed (but isn't fixed in the currently released version of MacPorts). The usual workaround is to just try again (as this usually works).

[jmroot (Joshua Root)]

Duplicate of #13930.

[(none)]

Milestone Port Bugs deleted