Message 28735 - Python tracker

➜

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.

Recipients
Author	goeran
Date	2006年06月08日.08:03:29
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to

Content
When using the Python engine shared library on HP-UX, I get error messages like these: /usr/lib/dld.sl: Unresolved symbol: sem_init (code) from /usr/local/lib/libpython2.4.sl Looking a bit closer, I realize that the shared Python library does not point to the librt library where these functions are defined. And this is specific for HP-UX. The rule in Makefile.pre.in to make libpython.so does refer to $(SHLIB). But the HP-UX specific rule to make libpython.sl does not. I suggest $(SHLIB) is added to the command to link libpython*.sl. Or alternatively, that these two rules are merged into one, parameterized by a variable holding the .so/.sl suffix.

Content

When using the Python engine shared library on HP-UX, I
get error messages like these:
/usr/lib/dld.sl: Unresolved symbol: sem_init (code) 
from /usr/local/lib/libpython2.4.sl
Looking a bit closer, I realize that the shared Python
library does not point to the librt library where these
functions are defined. And this is specific for HP-UX.
 The rule in Makefile.pre.in to make libpython*.so does
refer to $(SHLIB). But the HP-UX specific rule to make
libpython*.sl does not.
I suggest $(SHLIB) is added to the command to link
libpython*.sl. Or alternatively, that these two rules
are merged into one, parameterized by a variable
holding the .so/.sl suffix.

History
Date	User	Action	Args
2007年08月23日 14:40:27	admin	link	issue1502728 messages
2007年08月23日 14:40:27	admin	create

homepage