Python make issue

[skerr]

BPO	22045
Nosy	@Yhg1s, @tiran

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2022-01-24.23:57:01.223>
created_at = <Date 2014-07-23.12:17:42.215>
labels = ['type-bug', 'build']
title = 'Python make issue'
updated_at = <Date 2022-01-24.23:57:01.222>
user = 'https://bugs.python.org/skerr'

bugs.python.org fields:

activity = <Date 2022-01-24.23:57:01.222>
actor = 'iritkatriel'
assignee = 'none'
closed = True
closed_date = <Date 2022-01-24.23:57:01.223>
closer = 'iritkatriel'
components = ['Build']
creation = <Date 2014-07-23.12:17:42.215>
creator = 'skerr'
dependencies = []
files = []
hgrepos = []
issue_num = 22045
keywords = []
message_count = 2.0
messages = ['223736', '406915']
nosy_count = 4.0
nosy_names = ['twouters', 'christian.heimes', 'tshepang', 'skerr']
pr_nums = []
priority = 'normal'
resolution = 'out of date'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue22045'
versions = ['Python 2.7']

[skerr]

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?

[tiran]

Python 2 is no longer supported. Can you reproduce the issue with Python 3.9 or newer?