--enable-shared, how do i set the rpath?

[Mark Harrison]

I've built a python with --enable-shared in order to support mod_python,
but now I have to set LD_LIBRARY_PATH to $prefix/lib.

Worse, it seems mod_python will die on some import statements,
I'm suspecting ones that need to pull in .so's.

Any clues appreciated...
Mark.

--
Mark Harrison
Pixar Animation Studios

[Martin v. Löwis]

Re: --enable-shared, how do i set the rpath?

Mark Harrison schrieb:

I've built a python with --enable-shared in order to support mod_python,

Why do you think you have to build with --enable-shared to support
mod_python? I'd try to avoid --enable-shared if possible. It
has undesirable consequences...

but now I have to set LD_LIBRARY_PATH to $prefix/lib.

.... this being one of them. Actually, if you can pass -Wl,-rpath
correctly to the linkage of mod_python, you don't need
LD_LIBRARY_PATH , unless you move libpython2.5.so around.

Worse, it seems mod_python will die on some import statements,
I'm suspecting ones that need to pull in .so's.

You should inspect sys.path to find out whether it ought to find
those modules.

Regards,
Martin

[Robert Kern]

Re: --enable-shared, how do i set the rpath?

Mark Harrison wrote:

I've built a python with --enable-shared in order to support mod_python,
but now I have to set LD_LIBRARY_PATH to $prefix/lib.
>
Worse, it seems mod_python will die on some import statements,
I'm suspecting ones that need to pull in .so's.

I find that most of my Apache problems stem from incorrect permissions. Make
sure that the user running the Apache process has "read" and "execute"
permissions for the .so's.

--
Robert Kern

"I have come to believe that the whole world is an enigma, a harmless enigma
that is made terrible by our own mad attempt to interpret it as though it had
an underlying truth."
-- Umberto Eco