lcaminiti wrote
Stefan Teleman-2 wrote
-Qoption ccfe -features=gcc.
To build Boost with SunProCC you're going to have to pass several -Qoption ccfe -features=<X> to the compiler anyway. Might as well bite the bullet and pass them. :-) Otherwise, no dice, it won't build.
Also, the document page you are referring to shows an inconsistency between the typeof operator implementations in SunProC vs. SunProCC:
http://developers.sun.com/solaris/articles/c_type.html
SunProC allows typeof (without underscores) by default, without any special flags:
I see. I'll try to add your suggested options to my Jamfile and see how the regression tests go.
I've added this to ScopeExit test/Jamfile.v2: project : requirements <toolset>sun:<cxxflags>"-Qoption ccfe -features=gcc" ; But the regression test show: "/opt/sunstudio12.1/bin/CC" +d -library=stlport4 -features=tmplife -features=tmplrefstatic -library=stlport4 -g -erroff=%none -m64 -KPIC -DBOOST_ALL_NO_LIB=1 -I".." -c -o "/scratch2/kbelco/boost/results/boost/bin.v2/libs/scope_exit/test/world_checkpoint_seq.test/sun-5.10/debug/address-model-64/stdlib-sun-stlport/world_checkpoint_seq.o" "../libs/scope_exit/test/world_checkpoint_seq.cpp" Any idea why the -Qoptiona ccfee -features=gcc did not show up in the regression test run? What am I doing wrong? Thanks. --Lorenzo -- View this message in context: http://boost.2283326.n4.nabble.com/boost-scope-exit-trunk-tests-fail-on-sun-... Sent from the Boost - Dev mailing list archive at Nabble.com.