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.

Author r.david.murray
Recipients jgarrison, r.david.murray, tarek
Date 2009-04-04.07:24:51
SpamBayes Score 9.836352e-06
Marked as misclassified No
Message-id <1238829892.9.0.534365294446.issue5674@psf.upfronthosting.co.za>
In-reply-to
Content
Are you sure it isn't your Fedora installation that has the problem?  My
understanding is that the linker name (the libxxx.so name) should exist
and be a symbolic link to the most recent soname (libxxx.N).  So I think
distutils is doing the right thing.

See for example
http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html, the
first section of which (I didn't read the whole thing) matches my
understanding of how this works.

Do you have any doc pointers that says Fedora doesn't work this way?

(Note that the libxxx.so linker name may not be in the same directory as
the sonames or the actual library files.)
History
Date User Action Args
2009-04-04 07:24:53r.david.murraysetrecipients: + r.david.murray, tarek, jgarrison
2009-04-04 07:24:52r.david.murraysetmessageid: <1238829892.9.0.534365294446.issue5674@psf.upfronthosting.co.za>
2009-04-04 07:24:51r.david.murraylinkissue5674 messages
2009-04-04 07:24:51r.david.murraycreate