Re: Bug#72140: Setting up libraries too slow
> > > > On our university's Solaris systems, users have to set a library path
> > > > to get some software running correctly. Though I sometimes had the
> > > > impression that LD_LIBRARY_PATH didn't work as expected on Linux systems.
> > > > In Debian system, the LD_LIBRARY_PATH doesn't seem to be used much
> > > > though we do make use of preload path.
> > >
> > > Sounds like your university has a broken setup. If it users libraries
> > > in non-standard paths it should either add those to /etc/ld.so.conf,
> > > or use -rpath when compiling the apps that use them.o
> > AFAIK, Solaris does not have an /etc/ld.so.conf. The run-time library search
> > path goes something like:
> > 1. LD_LIBRARY_PATH
> > 2. paths specified at link time (-R)
> > 3. /usr/lib
Worse still, in case LD_LIBRARY_PATH is set, the built-in paths are
ignored intentionally. You have one broken program, you break them all
(and this can only be fixed on a per-binary wrapper script).
The Solaris linker also recognizes the LD_RUN_PATH environment
variable, which is treated as if additional -R options were given.
AFAIK compiling '-L/some:/path -Xlinker -R/some:/path' is the only other
method that works on both Solaris and Linux (where the middle item can be
dropped only on Solaris).
Karsten Tinnefeld email@example.com
Fachbereich Informatik, Lehrstuhl 2 T +49 231 755-4737
Universität Dortmund, D-44221 Dortmund, Deutschland F +49 231 755-2047