Re: [Boost-build] v2/gcc LD_LIBRARY_PATH not set correctly for python tests

From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-06-04 02:58:18

On Friday 02 June 2006 13:13, Markus Schöpflin wrote:
> When gcc is installed in a non-default location, bb.v2 sets the
> LD_LIBRARY_PATH when tests are executed. For example:
>
> ...
>
> testing.capture-output
> ../../../../bin.v2/libs/algorithm/string/test/split.test/gcc-4_0_3_tru64/de
>bug/split.run
>
>
> LD_LIBRARY_PATH=/opt/gcc-4.0.3/lib:/opt/gcc-4.0.3/lib32:/opt/gcc-4.0.3/lib6
>4:$LD_LIBRARY_PATH export LD_LIBRARY_PATH
>
>
> ../../../../bin.v2/libs/algorithm/string/test/split.test/gcc-4_0_3_tru64/de
>bug/split
>
> ../../../../bin.v2/libs/algorithm/string/test/split.test/gcc-4_0_3_tru64/de
>bug/split.output 2>&1
>
> ...
>
> This is missing when python tests are executed:

Hi Markus,
that's for diagnosing this! I've just comitted a fix for this to trunk and 
branch. Can you please check that it works for you?

Thanks,
Volodya

-- 
Vladimir Prus
http://vladimir_prus.blogspot.com
Boost.Build V2: http://boost.org/boost-build2