On Tue, Apr 14, 2009 at 10:19:43AM -0400, Wesley Chow wrote:
On Apr 14, 2009, at 4:58 AM, Joerg Sonnenberger wrote:
On Mon, Apr 13, 2009 at 05:46:56PM -0400, Wesley Chow wrote:
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.
Can you run "objdump -p python2.5"? What is the rpath it is
listening?
/usr/lib64:/usr/pkg/lib
Is there any way to swap those?
Can you look into .work.log for the actual link command (e.g. grep for
"-o python2.5 ") and copy the <.> line?