Opened 13 years ago
Closed 11 years ago
#32343 closed defect (fixed)
python32: inconsistent naming of libraries
Reported by: | jknockaert (Jasper Knockaert) | Owned by: | jyrkiwahlstedt |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.0.3 |
Keywords: | Cc: | ||
Port: | python32 |
Description
Build scripts use python3.2-config to determine the libraries to link against. When doing python3.2-config --libs, the script returns a reference to -lpython3.2m which does not exist in the macports build of Python 3.2.
A solution would be to add a symbolic link for both the static and the dynamic library in order to cover both the legacy naming scheme (without the abiflag 'm') and the config3.2-python provided one.
Change History (3)
comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Owner: | changed from macports-tickets@… to jwa@… |
---|---|
Port: | python32 added |
Summary: | inconsistent naming of python3.2 libraries → python32: inconsistent naming of libraries |
comment:2 Changed 11 years ago by jmroot (Joshua Root)
comment:3 Changed 11 years ago by jmroot (Joshua Root)
Resolution: | → fixed |
---|---|
Status: | new → closed |
libpython3.2m.dylib exists in version 3.2.5.
Note: See
TracTickets for help on using
tickets.
Upstream bug: http://bugs.python.org/issue14197