On 02/26/11 16:40, Michael Caisse wrote:
On 02/26/2011 01:55 PM, Larry Evans wrote:
On 02/26/11 15:25, Michael Caisse wrote:
Hi Larry -
FWIW, I think most of us test libraries under review by placing them within a boost source tree. Is there a reason that this approach is not acceptable?
Well, I just hadn't thought of that. IOW, I'd move:
/home/evansl/prog_dev/boost-svn/ro/trunk/sandbox/ro/SOC /2010/phoenix3/libs/phoenix
to:
/home/evansl/prog_dev/boost-svn/ro/trunk/libs/phoenix
and:
/home/evansl/prog_dev/boost-svn/ro/trunk/sandbox/ro/SOC /2010/phoenix3/boost/phoenix
to:
/home/evansl/prog_dev/boost-svn/ro/trunk/boost/phoenix
and then run the tests?
Correct.
Would the svn update still work?
Yes. You would need to run 'svn update' in each directory (boost/phoenix and libs/phoenix).
Did that, but it doesn't avoid the error messages about macro arity: default-directory: "~/prog_dev/boost-svn/ro/trunk/libs/phoenix/test/" -*- Compilation started at Sat Feb 26 16:54:51 bjam phoenix_core warning: No toolsets are configured. warning: Configuring default toolset "gcc". warning: If the default is wrong, your build may not work correctly. warning: Use the "toolset=xxxxx" option to override our guess. warning: For more configuration options, please consult warning: http://boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html ...patience... ...found 786 targets... ...updating 10 targets... common.mkdir ../../../bin.v2/libs/phoenix common.mkdir ../../../bin.v2/libs/phoenix/test common.mkdir ../../../bin.v2/libs/phoenix/test/primitives_tests.test common.mkdir ../../../bin.v2/libs/phoenix/test/primitives_tests.test/gcc-4.4.3 common.mkdir ../../../bin.v2/libs/phoenix/test/primitives_tests.test/gcc-4.4.3/debug common.mkdir ../../../bin.v2/libs/phoenix/test/primitives_tests.test/gcc-4.4.3/debug/core gcc.compile.c++ ../../../bin.v2/libs/phoenix/test/primitives_tests.test/gcc-4.4.3/debug/core/primitives_tests.o In file included from ../../../boost/proto/matches.hpp:33, from ../../../boost/phoenix/core/meta_grammar.hpp:15, from ../../../boost/phoenix/core/is_nullary.hpp:15, from ../../../boost/phoenix/core/actor.hpp:18, from ../../../boost/phoenix/core/argument.hpp:13, from core/primitives_tests.cpp:10: ../../../boost/mpl/aux_/template_arity.hpp:86:1: error: macro "BOOST_PP_TUPLE_ELEM_2_0" requires 2 arguments, but only 1 given ../../../boost/mpl/aux_/template_arity.hpp:86:1: error: macro "BOOST_PP_SEQ_ELEM_III" requires 2 arguments, but only 1 given ../../../boost/mpl/aux_/template_arity.hpp:86:1: error: macro "BOOST_PP_SEQ_ELEM_III" requires 2 arguments, but only 1 given ../../../boost/mpl/aux_/template_arity.hpp:86:1: error: macro "BOOST_PP_SEQ_ELEM_III" requires 2 arguments, but only 1 given ../../../boost/mpl/aux_/template_arity.hpp:86:1: error: macro "BOOST_PP_SEQ_ELEM_III" requires 2 arguments, but only 1 given . . . core/primitives_tests.cpp: In function 'int main()': core/primitives_tests.cpp:70: error: no match for call to '(const boost::phoenix::actor<boost::proto::exprns_::expr<boost::proto::tag::terminal, boost::proto::argsns_::term<boost::phoenix::detail::argument<1> >, 0l>
) (const int&)'
"g++" -ftemplate-depth-128 -O0 -fno-inline -Wall -g -fPIC -DBOOST_ALL_NO_LIB=1 -I"../../.." -c -o "../../../bin.v2/libs/phoenix/test/primitives_tests.test/gcc-4.4.3/debug/core/primitives_tests.o" "core/primitives_tests.cpp" ...failed gcc.compile.c++ ../../../bin.v2/libs/phoenix/test/primitives_tests.test/gcc-4.4.3/debug/core/primitives_tests.o... . . .