[Boost-build] [python] [bbv2] py-run vs. bpl-test

From: Markus Schöpflin (markus.schoepflin_at_[hidden])
Date: 2006-09-26 03:45:43

Hello,

I'm currently investigating the last remaining python test failures on the 
RC branch for the re-added HP TestDrive test runner.

There are five failures left, and every single one of them fails with the 
following error:

     "/usr/local/gcc-3.4.4/bin/g++" 
-L"/usr/users/boost/opt/Python-2.4.3/lib/python2.4/config" -Wl,-rpath 
-Wl,"/boost/regression/results/boost/bin.v2/libs/python/build/gcc-3_4_4_tru64/debug" 
  -o 
"/boost/regression/results/boost/bin.v2/libs/python/test/pointee.test/gcc-3_4_4_tru64/debug/pointee" 
 
"/boost/regression/results/boost/bin.v2/libs/python/test/pointee.test/gcc-3_4_4_tru64/debug/pointee.o" 
"/boost/regression/results/boost/bin.v2/libs/python/build/gcc-3_4_4_tru64/debug/libboost_python-gcc-gd-1_34.so.1.34.0" 
   -lpthread -lrt -lpython2.4  -g -mieee -s

deflate
deflateEnd
inflate
inflateEnd
adler32
crc32
deflateInit_
deflateInit2_
inflateInit2_
collect2: ld returned 1 exit status

This looks like libz is missing from the linker command line.

Interestingly, all of the failing tests either use the jam rule run or 
py-run. All tests using the rule bpl-test are working fine.

And the toolset gcc-4.1.1_sunos_i86pc shows failures for the same tests, 
although the exact error is different.

What is the intended difference between these two test rules? Why isn't 
there just one test rule? And does anyone know why it works in one case, 
but not the other?

Thanks, Markus