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 ned.deily
Recipients ned.deily, ubehera
Date 2016-08-04.20:19:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1470341997.1.0.222285274447.issue27685@psf.upfronthosting.co.za>
In-reply-to
Content
No doubt you are running into same problem that is described here: http://stackoverflow.com/questions/12553057/compile-python-2-7-3-from-source-on-a-system-with-python-2-7-already

The problem is, that on most Unix systems (with the notable exception of Mac OS X), the path to shared libraries is not an absolute path.  So, if you install Python in a non-standard location, which is the right thing to do so as not to interfere with a system Python of the same version, you will need to configure in the path to the shared library or supply it via an environment variable at run time, like LD_LIBRARY_PATH.  You may be better off avoiding --enable-shared; it's easy to run into problems like this with it.
History
Date User Action Args
2016-08-04 20:19:57ned.deilysetrecipients: + ned.deily, ubehera
2016-08-04 20:19:57ned.deilysetmessageid: <1470341997.1.0.222285274447.issue27685@psf.upfronthosting.co.za>
2016-08-04 20:19:57ned.deilylinkissue27685 messages
2016-08-04 20:19:56ned.deilycreate