Re: [Boost-build] [V2] Executing a test doesn't adjust LD_LIBRARY_PATH

From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-03-10 01:45:18

On Wednesday 08 March 2006 12:32, Markus Schöpflin wrote:
> V1 used to adjust LD_LIBRARY_PATH when running tests with the GCC toolset:
>
> bjam -sTOOLS=gcc-4.0.2-osf1 -d+2 bind_visit_test
>
> [...]
>
> execute-test
> ../../../bin/boost/libs/bind/test/bind_visit_test.test/gcc-4.0.2-osf1/debug
>/bind_visit_test.run
>
>      LD_LIBRARY_PATH=/opt/gcc-4.0.2/lib

So, it's adding path to gcc library directories? Why exactly this is needed? 
Can you add this directory to global LD_LIBRARY_PATH, and if no, why?

Say, if I build an application with gcc-4.0.2 and it won't run right away 
because gcc libraries are not in LD_LIBRARY_PATH, then the compiler is not 
fully usable. Boost.Build can work around this, but is it better than putting 
extra directory to LD_LIBRARY_PATH?

BTW, can you also tell how you configure gcc-4.0.2 with V1? That is, what's 
the content of the toolset file?

- Volodya