build errors with 1.54 on linux
Hello All, I am building boost 1.54 on a linux box and I am seeing the following error messages after the build: gcc.compile.c++ bin.v2/libs/wave/build/gcc-4.7/release/link-static/threading-multi/instantiate_re2c_lexer_str.o gcc.compile.c++ bin.v2/libs/wave/build/gcc-4.7/release/link-static/threading-multi/token_ids.o gcc.compile.c++ bin.v2/libs/wave/build/gcc-4.7/release/link-static/threading-multi/wave_config_constant.o common.mkdir bin.v2/libs/wave/build/gcc-4.7/release/link-static/threading-multi/cpplexer common.mkdir bin.v2/libs/wave/build/gcc-4.7/release/link-static/threading-multi/cpplexer/re2clex gcc.compile.c++ bin.v2/libs/wave/build/gcc-4.7/release/link-static/threading-multi/cpplexer/re2clex/aq.o gcc.compile.c++ bin.v2/libs/wave/build/gcc-4.7/release/link-static/threading-multi/cpplexer/re2clex/cpp_re.o gcc.archive bin.v2/libs/wave/build/gcc-4.7/release/link-static/threading-multi/libboost_wave.a common.copy /home/yadav/dev/cpp/boost_1.54/lib/libboost_wave.a ...failed updating 29 targets... ...updated 10797 targets... How can I know what these 29 targets have failed and how to go about getting a clean build? Thanks!
On Fri, Sep 20, 2013 at 08:37:24PM -0400, Dev Guy wrote:
Hello All,
I am building boost 1.54 on a linux box and I am seeing the following error messages after the build:
gcc.compile.c++ bin.v2/libs/wave/build/gcc-4.7/release/link-static/threading-multi/instantiate_re2c_lexer_str.o [snip] gcc.compile.c++ bin.v2/libs/wave/build/gcc-4.7/release/link-static/threading-multi/cpplexer/re2clex/cpp_re.o gcc.archive bin.v2/libs/wave/build/gcc-4.7/release/link-static/threading-multi/libboost_wave.a common.copy /home/yadav/dev/cpp/boost_1.54/lib/libboost_wave.a ...failed updating 29 targets... ...updated 10797 targets...
How can I know what these 29 targets have failed and how to go about getting a clean build?
None of those lines you mentioned are ones that failed. If you run the build again, only the remaining (failed or otherwise omitted) targets will be built. Unlike other popular build systems, Boost's build continues trying to build the other libraries on failures, as it's expected to be some failures here and there. You can also pass -q to b2 (bjam) to make it stop on the first failure. -- Lars Viklund | zao@acc.umu.se
participants (2)
-
Dev Guy
-
Lars Viklund