This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author wempa
Recipients wempa
Date 2013-05-20.20:11:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1369080710.44.0.400005629221.issue18024@psf.upfronthosting.co.za>
In-reply-to
Content
I recently built a new version of our Linux tools using Python 2.7.5 on our SLES11SP2 server.  Afterwards, I noticed that the dbm module was not built successfully.  The Python build did not fail and the failed module build summary at the end of the build did not list "dbm", which surprised me.  I rebuilt Python and captured the actual error when attempting to build the dbm module.  Below is the error.  I managed to get it to build by replacing "-lndbm" with "-lgdbm".  This is the first time dbm has failed to build on this platform.  I've built several versions of Python 2.7.2, 2.7.3 and 2.7.4 and this module built every single time.  Something that has changed in the build process is causing this problem.



Link Error:

gcc -pthread -shared build/temp.linux-x86_64-2.7/nfs/statbuild/ci1admin/ci1_toolchain_src/KRIS/Python-2.7.5/Modules/dbmmodule.o -L/usr/lib -L/lib -L/usr/x86_64-suse-linux/lib -L/lib64 -L/usr/lib64 -L/usr/local/lib -lndbm -o build/lib.linux-x86_64-2.7/dbm.so
/usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld: skipping incompatible /usr/lib/libgdbm.so when searching for /usr/lib/libgdbm.so
/usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld: cannot find /usr/lib/libgdbm.so
collect2: ld returned 1 exit status
History
Date User Action Args
2013-05-20 20:11:50wempasetrecipients: + wempa
2013-05-20 20:11:50wempasetmessageid: <1369080710.44.0.400005629221.issue18024@psf.upfronthosting.co.za>
2013-05-20 20:11:50wempalinkissue18024 messages
2013-05-20 20:11:50wempacreate