Author jdemeyer
Recipients eric.araujo, jdemeyer, tarek
Date 2012-06-25.13:42:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1340631736.41.0.714328941122.issue15182@psf.upfronthosting.co.za>
In-reply-to
Content
The find_library_function() in Lib/distutils/unixccompiler.py does a very simple-minded check to determine the existence of a library. It basically only checks that a certain .so file exists. This may lead to false positives: the mere existence of a .so file does not imply that we can actually link against that library.

In addition to (or even better: instead of) checking the existence of the file, you should try to (in the spirit of autoconf) compile a simple program using $CC -l$LIB prog.c -o prog

One particular instance of where things can go wrong is with a 32-bit/64-bit multilib installation. Python might find a 64-bit library in /usr/lib when we're actually compiling 32-bit with libraries in /usr/lib32.
History
Date User Action Args
2012-06-25 13:42:16jdemeyersetrecipients: + jdemeyer, tarek, eric.araujo
2012-06-25 13:42:16jdemeyersetmessageid: <1340631736.41.0.714328941122.issue15182@psf.upfronthosting.co.za>
2012-06-25 13:42:12jdemeyerlinkissue15182 messages
2012-06-25 13:42:11jdemeyercreate