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

From: Markus Schöpflin (markus.schoepflin_at_[hidden])
Date: 2006-06-02 05:13:28

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/debug/split.run

 
LD_LIBRARY_PATH=/opt/gcc-4.0.3/lib:/opt/gcc-4.0.3/lib32:/opt/gcc-4.0.3/lib64:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH

 
../../../../bin.v2/libs/algorithm/string/test/split.test/gcc-4_0_3_tru64/debug/split 
   > 
../../../../bin.v2/libs/algorithm/string/test/split.test/gcc-4_0_3_tru64/debug/split.output 
2>&1

...

This is missing when python tests are executed:

...

 
LD_LIBRARY_PATH=/vol2/boost/src/boost-RC_1_34_0/bin.v2/libs/python/build/gcc-4_0_3_tru64/debug/threading-multi:/vol2/boost/src/boost-RC_1_34_0/bin.v2/libs/python/test/str.test/gcc-4_0_3_tru64/debug/threading-multi:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH

 
PYTHONPATH=../../../bin.v2/libs/python/test/str.test/gcc-4_0_3_tru64/debug/threading-multi:$PYTHONPATH
export PYTHONPATH

...

This prevents the python tests from working in this configuration. Maybe 
this should be fixed before 1.34 is released.

Markus