classification
Title: Python make issue
Type: behavior Stage:
Components: Build Versions: Python 2.7
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: christian.heimes, skerr, tshepang, twouters
Priority: normal Keywords:

Created on 2014-07-23 12:17 by skerr, last changed 2021-11-24 09:51 by christian.heimes.

Messages (2)
msg223736 - (view) Author: Shannon Kerr (skerr) Date: 2014-07-23 12:17
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?
msg406915 - (view) Author: Christian Heimes (christian.heimes) * (Python committer) Date: 2021-11-24 09:51
Python 2 is no longer supported. Can you reproduce the issue with Python 3.9 or newer?
History
Date User Action Args
2021-11-24 09:51:29christian.heimessetnosy: + christian.heimes
messages: + msg406915
2021-11-24 07:49:43iritkatrielsetnosy: + twouters
2014-07-25 19:23:45tshepangsetnosy: + tshepang
2014-07-23 12:19:42skerrsettype: compile error -> behavior
2014-07-23 12:19:27skerrsettype: compile error
2014-07-23 12:17:42skerrcreate