> Ian, please take a look at 'bjam.log'. I'm pretty
sure there's some
> error
> message there.
The last 10 lines of bjam.log seem look to me like a
normally
completing bjam build.
% tail results/bjam.log
"g++" -ftemplate-depth-100 -O0 -fno-inline
-Wall -g -fPIC -
dynamic -Wno-long-double -no-cpp-precomp -arch ppc64 -
DBOOST_ALL_NO_LIB=1 -I".." -c -o
"/private/var/automount/home/
ianfasel/SCTL/boost_regressions/results/boost/bin.v2/libs/xp
ressive/
test/test_sub_match.test/darwin-4.0/debug/test_sub_match.o&
quot; "../libs/
xpressive/test/test_sub_match.cpp"
**passed** /private/var/automount/home/ianfasel/SCTL/
boost_regressions/results/boost/bin.v2/libs/xpressive/test/
test_sub_match.test/darwin-4.0/debug/test_sub_match.test
echo passed >
/private/var/automount/home/ianfasel/SCTL/
boost_regressions/results/boost/bin.v2/libs/xpressive/test/
test_sub_match.test/darwin-4.0/debug/test_sub_match.test
...failed updating 231 targets...
...skipped 2326 targets...
...updated 10793 targets...
Of course I see that various things failed, but it doesn't
look like
regression.py itself should have failed. And the files such
as
"results/boost/bin.v2/libs/xpressive/test/test_sub_mat
ch.test/
darwin-4.0/debug/test_sub_match.test" certainly were
created.
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
a>
|