Boost Testing :
Subject: Re: [Boost-testing] pathscale 3.1 reporting problems?
From: K. Noel Belcourt (kbelco_at_[hidden])
Date: 2009-06-23 15:59:33
Another try at diagnosing this problem (please disregard my previous
postings on this subject).
On Jun 13, 2009, at 12:02 PM, Steven Watanabe wrote:
> According to http://tinyurl.com/nunary, the test library fail to
> but following the
> link, it appears that the test library did build correctly.
It seems that the pathscale-3.1 tuple another_tuple_test_bench test
failed to link for a lack of libboost_test_exec_monitor-31-d-1_40.a,
which itself failed to build because unit_test_main.o failed to compile.
So there's two issues here. First, I could use a little help
figuring out why unit_test_main.o fails to compile for
pathscale-3.1. The second issue is parsing the nightly bjam.log
output from the pathscale-3.1 toolset seems to be rather messed up,
though not sure why at the moment (the parsing seems to work better
Here's the compilation failure of unit_test_main.o.
"/usr/local/pathscale-3.1/bin/pathCC" -noinline -g -Wall -
DBOOST_ALL_NO_LIB=1 -I".." -c -o "/var/scratch/boost/results/boost/
In file included from ../boost/test/utils/iterator/token_iterator.hpp:
../boost/test/utils/named_params.hpp: In member function `ReferenceType
RefType>::operator(boost::nfp::keyword<unique_id, true>) const':
../boost/test/utils/named_params.hpp:190: error: syntax error before