[Gllug] Any BSD users on here?

[Steve Nicholson]

Hi
thanks for the replies, setting LD_LIBRARY_PATH: works but I've found
it's not set in the environment after I log out and since it's going to
be used by Zope I guess it's not the best solution.  I can get
everything to compile now by putting the right paths in the config files
but on importing the module into python I get errors it can't find the
library file.  If I set the LD_LIBRARY_PATH it's works ok, so I need to
figure out how to get it right from the compiling end I guess.

>From reading http://www.netbsd.org/Documentation/elf.html I think I need
to add -rpath /usr/local/lib to the linker but not too sure where/how I
go about this.  I would like to learn the right way to do it so I don't
go causing other problems later on.

thanks again for the replies.
Steve.

On Thu, 23 Jan 2003 22:02:46 +0000 (GMT) chris.wareham at btopenworld.com
chris.wareham at btopenworld.com wrote:
> ldconfig is a hangover from the pre-ELF days, and has been
> consigned to supporting a.out libraries on the BSD's. Compile your
> apps so they know where to look for libraries, and your libraries
> so they know where they live. For a decent tutorial on the way ELF
> shared libraries are found, see:
> 
>   http://www.netbsd.org/Documentation/elf.html
> 
> A short cut to the "lazy" Linux behaviour is to add the library
> paths to LD_LIBRARY_PATH:
> 
>   export LD_LIBRARY_PATH=/usr/X11R6/lib:/usr/local/lib
> 
> This should cover any hand compiled libraries that make the
> Linux-centric assumption that the linker maintains a database of
> shared libraries based on paths in /etc/ld.so.conf.
> 
> Chris

-- 
Gllug mailing list  -  Gllug at linux.co.uk
http://list.ftech.net/mailman/listinfo/gllug