>Yes, I remember. Usually LD_LIBRARY_PATH is a variable for the _dynamic_
>linker (ld.so) while -L is for the linker program. But perhaps on your system
>"ld" looks alternatively inside LD_LIBRARY_PATH, too. Hmmm.. yes, this could
>be also the root of your problems. I've fixed it now for 2.1.1, so we will see
>if you need LD_LIBRARY_PATH in the future again. If yes, please complain
>again. Because usually it should be _not_ needed.
This is the reason why it is rather problematic to have LD_LIBRARY_PATH
set as a developer, it is much better to tell the linker via the run
path option where to find the modules at runtime as to rely on
LD_LIBRARY_PATH. If I encounter a program that forces me to the
LD_LIBRARY_PATH, I commonly wrap up the call to the program in a script
that sets the LD_LIBRARY_PATH just before calling the program. This way
the environment stays clean.
Jens-Uwe Mager
HELIOS Software GmbH
Steinriede 3
30827 Garbsen
Germany
Phone: +49 5131 709320
FAX: +49 5131 709325
Internet: [EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
