[Boost-build] [UBLAS] [RC_1_34] Reason for large scale test failure

From: Markus Schöpflin (markus.schoepflin_at_[hidden])
Date: 2006-06-07 08:28:33

Here is the log of a manual execution of the UBLAS test1 test:

---%<---
/vol2/boost/src/boost-RC_1_34_0/libs/numeric/ublas/test> bjam --v2 
gcc-4_0_3_tru64 test1
Building Boost.Regex with the optional Unicode/ICU support disabled.
Please refer to the Boost.Regex documentation for more information
(and if you don't know what ICU is then you probably don't need it).
...patience...
...found 389 targets...
...updating 14 targets...
MkDir1 ../../../../bin.v2/libs/numeric
MkDir1 ../../../../bin.v2/libs/numeric/ublas
MkDir1 ../../../../bin.v2/libs/numeric/ublas/test
MkDir1 ../../../../bin.v2/libs/numeric/ublas/test/test1.test
MkDir1 ../../../../bin.v2/libs/numeric/ublas/test/test1.test/gcc-4_0_3_tru64
MkDir1 
../../../../bin.v2/libs/numeric/ublas/test/test1.test/gcc-4_0_3_tru64/debug
MkDir1 
../../../../bin.v2/libs/numeric/ublas/test/test1.test/gcc-4_0_3_tru64/debug/test1
gcc.compile.c++ 
../../../../bin.v2/libs/numeric/ublas/test/test1.test/gcc-4_0_3_tru64/debug/test1/test1.o
gcc.compile.c++ 
../../../../bin.v2/libs/numeric/ublas/test/test1.test/gcc-4_0_3_tru64/debug/test1/test11.o
gcc.compile.c++ 
../../../../bin.v2/libs/numeric/ublas/test/test1.test/gcc-4_0_3_tru64/debug/test1/test12.o
gcc.compile.c++ 
../../../../bin.v2/libs/numeric/ublas/test/test1.test/gcc-4_0_3_tru64/debug/test1/test13.o
gcc.link 
../../../../bin.v2/libs/numeric/ublas/test/test1.test/gcc-4_0_3_tru64/debug/test1
/usr/bin/ld:
Can't create output file (Is a directory)
collect2: ld returned 1 exit status

     "/opt/gcc-4.0.3/bin/g++"    -o 
"../../../../bin.v2/libs/numeric/ublas/test/test1.test/gcc-4_0_3_tru64/debug/test1" 
 
"../../../../bin.v2/libs/numeric/ublas/test/test1.test/gcc-4_0_3_tru64/debug/test1/test1.o" 
"../../../../bin.v2/libs/numeric/ublas/test/test1.test/gcc-4_0_3_tru64/debug/test1/test11.o" 
"../../../../bin.v2/libs/numeric/ublas/test/test1.test/gcc-4_0_3_tru64/debug/test1/test12.o" 
"../../../../bin.v2/libs/numeric/ublas/test/test1.test/gcc-4_0_3_tru64/debug/test1/test13.o" 
     -g -mieee

...failed gcc.link 
../../../../bin.v2/libs/numeric/ublas/test/test1.test/gcc-4_0_3_tru64/debug/test1...
...skipped 
<p../../../../bin.v2/libs/numeric/ublas/test/test1.test/gcc-4_0_3_tru64/debug>test1.run 
for lack of 
<p../../../../bin.v2/libs/numeric/ublas/test/test1.test/gcc-4_0_3_tru64/debug>test1...
...failed updating 1 target...
...skipped 2 targets...
...updated 11 targets...
--->%---

This test is specified in the jam file as follows:

test-suite numeric/uBLAS
     : [ run test1/test1.cpp
             test1/test11.cpp
             test1/test12.cpp
             test1/test13.cpp
         : # args
         : # input files
         : # requirements
             <define>$(UBLAS_TESTSET)
       ]
       ...

It looks like BBv2 somehow forgets the extra test1 when generating the name 
for the executable. IOW, instead of generating .../debug/test1/test1 it 
generates .../debug/test1 which of course collides with the directory name 
of the test which happens to be .../debug/test1.

An obvious workaround is to rename either the test1 directory or the test1 
source file where the name is generated from to something else, but maybe 
this is better fixed in BBv2.

Markus