[Python-Dev] issue 9807 - a glitch in coexisting builds of different types (original) (raw)
Jeroen Ruigrok van der Werven asmodai at in-nomine.org
Tue Oct 5 10:50:57 CEST 2010
- Previous message: [Python-Dev] issue 9807 - a glitch in coexisting builds of different types
- Next message: [Python-Dev] issue 9807 - a glitch in coexisting builds of different types
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
-On [20101004 22:03], Barry Warsaw (barry at python.org) wrote:
We already have libpython3.2.so.1.0 which also doesn't end in .so. I suppose we could put the build flags before the .so. part, but I think Matthias had a problem with that (I don't remember the details).
Using major and minor numbers after the .so designation is an old aout (de facto) standard. ELF settled on just major numbers. And typically you will find a symbolic link from libwhatever.so to libwhatever.so.1
Also, from FreeBSD's ldconfig manual page:
"Filenames must conform to the lib*.so.[0-9] pattern in order to be added to the hints file."
So ending a shared object with the build flags will cause problems on FreeBSD and probably the other BSDs (DragonFly, NetBSD, OpenBSD) and most likely Mac OS X as well.
-- Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai イェルーン ラウフロック ヴァン デル ウェルヴェン http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B Time is merely a residue of Reality...
- Previous message: [Python-Dev] issue 9807 - a glitch in coexisting builds of different types
- Next message: [Python-Dev] issue 9807 - a glitch in coexisting builds of different types
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]