[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: problem installing python25 on Debian lenny
Sorry, meant to reply to list.
On Apr 13, 2009, at 5:46 PM, Wesley Chow wrote:
No, it should really be just 5KB as it is dynamically linked.
What you might be seeing is a conflict in the library search path,
for some reason it is picking up the version in /usr/lib on Linux.
Given that ELF linkage is more often than not broken in Linux because
distro maintaners don't understand it, I wouldn't be surprised too
Ah, you're right, ldd is showing that python2.5 has a dependency on
libpython2.5.so.1.0, and it appears that it's getting picked up in /
usr/lib64, which is where the native system has its python shared
object. It appears that manually building form the Python source
produces a statically linked exec, so that's why that method works.
Removing the --enable-shared option from the lang/python25's
Makefile fixes the problem.
In general, though, is there some way to build an executable with
information about where it should look for shared libraries, instead
of relying on the system to do that? In other words, is there a way
to build /usr/pkg/bin/python2.5 to look in /usr/pkg/lib, without
overriding the search path for everything?
Main Index |
Thread Index |