Author skerr
Recipients skerr
Date 2014-07-23.12:17:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1406117862.23.0.135696000898.issue22045@psf.upfronthosting.co.za>
In-reply-to
Content
If you execute the following commands on a system that doesn’t already have Python 2.7.X installed on it, it will result in bloated libs that statically link libpythyon2.7.a instead of the locally built libpython2.7.so:

./configure
make
sudo make install
./configure —enable-shared
make
sudo make install


Due to the library search path order in the Python build tools being:
-L /usr/local/lib -L .
the first lib found is in /usr/local/lib and it is the static library, so this is used to link.  This results in, for example, cPickle.so being 4.9M instead of 188K.

Shouldn't the just-built local library be used before anything on the system?
History
Date User Action Args
2014-07-23 12:17:42skerrsetrecipients: + skerr
2014-07-23 12:17:42skerrsetmessageid: <1406117862.23.0.135696000898.issue22045@psf.upfronthosting.co.za>
2014-07-23 12:17:42skerrlinkissue22045 messages
2014-07-23 12:17:41skerrcreate