|
Boost-Build : |
From: Martin Wille (mw8329_at_[hidden])
Date: 2004-09-19 12:58:29
Christoph Ludwig wrote:
>
> Of course, these are obvious questions when one needs to track down
> problems with shared libraries but let me ask them anyway:
>
> What does `ldd' report for the executable in question? Can it resolve
> the dependencies?
No, it can't (see below)
> If not, /usr/local/gcc-2.95.3/lib/ does not look like a default library
> path. (According to the ld.so(8) man page on my Linux system the only
> default paths are /lib and /usr/lib.)
right, it isn't.
Is it mentioned in
> /etc/ld.so.conf or in LD_LIBRARY_PATH? (AFAICT, gcc does not link
> against its own runtime libraries with `-rpath'. If I test programs
> built with different compiler versions I always need to set
> LD_LIBRARY_PATH because I keep the respective runtime libraries in
> separate directories not listed in /etc/ld.so.conf.)
You're right with that, of course. However, Boost.Test is supposed to
setup LD_LIBRARY_PATH to point to /usr/local/gcc-2.95.3/lib in this
case when running the test.
Regards,
m
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk