Boost Testing :
From: John Maddock (john_at_[hidden])
Date: 2006-07-12 05:38:55
There are quite a few TR1 tests that are failing with sunpro, that appear to
be an include path problem. I believe this was working OK with bbv1, but
the include paths appear to be coming out in the wrong order with the
A typical list of errors here: http://tinyurl.com/pcwf5 suggests that the
"real" version of <memory> is getting included rather than the Tr1 version.
The command line shows that the TR1 headers are in the path, but *after* the
Boost include path, and while I'm not completely sure, I believe this is the
problem (I've seen issues like this before, but they're really hard to
diagnose without spending way too much time studying pre-processor outputs).
So... anyone any ideas why the toolset is injecting the boost path ahead of
other <include> directives?