➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: bad value of INSTSONAME in Makefile
Type: Stage:
Components: Build Versions: Python 2.3
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: lanclos, loewis
Priority: normal Keywords:

Created on 2003-10-16 05:05 by lanclos, last changed 2022-04-10 16:11 by admin. This issue is now closed.

Messages (2)
msg18650 - (view) Author: Kyle Lanclos (lanclos) Date: 2003-10-16 05:05 
With the 2.3.2 source on a Solaris 9 machine and the
following configure:

./configure --prefix=/opt/python-2.3.2 --enable-shared

'make; make install' will result in an error when the
Makefile tries to link the .so file, because INSTSONAME
= LDLIBRARY = libpython$(VERSION).so, and the linker
tries to do:

$(INSTALL_SHARED) libpython$(VERSION)$(SO)
$(DESTDIR)$(LIBDIR)/$(INSTSONAME);

(cd $(DESTDIR)$(LIBDIR); $(LN) -sf $(INSTSONAME)
libpython$(VERSION)$(SO));

This is all fine and good, except that
libpython$(VERSION)$(SO) is the same as INSTSONAME, and
you end up doing:

ln -sf libpython2.3.so libpython2.3.so

...which rightfully returns an error. Looking at the
generated Makefile on Linux, the value of INSTSONAME is:

INSTSONAME=     libpython$(VERSION).so.1.0

...instead of this value from Solaris:

INSTSONAME=     $(LDLIBRARY)
msg18651 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2003-11-19 19:57 
Logged In: YES 
user_id=21627

This is fixed with patch #841807.
History
Date User Action Args
2022-04-10 16:11:45adminsetgithub: 39416
2003-10-16 05:05:19lancloscreate