b2 returns code 256 exit code instead zero

[pavel.odintsov@…]

Hello!

I'm using b2 from boost_build1.5.8 and run it with flags: Command HOME=/root PATH=$PATH:/opt/fastnetmon/libraries/gcc520/bin /opt/fastnetmon/libraries/boost_build1.5.8/bin/b2 -j8 -sICU_PATH=/opt/fastnetmon/libraries/libicu_56_1 --build-dir=/tmp/fastnetmon.build.dir.DvDYep6dMm/boost_build_temp_directory_1_5_8 toolset=gcc-5.2 link=shared --without-test --without-python --without-wave --without-graph --without-coroutine --without-math --without-log --without-graph_parallel --without-mpi

But I get 256 instead zero in case of correct exit.

Could you fix this?

[anonymous]

As you can see I'm using custom compiler for Boost building. It could make sense.

[Steven Watanabe]

Are you sure that this is wrong? You need to use WIFEXITED and WEXITSTATUS to get the actual exit code (which should be less than 256) from the status indicated by wait.

[pavel.odintsov@…]

I'm checking exit code with echo $? and it could handle exit code in proper way (and it doing this perfectly for other tools). So I'm definitely sure about broken exit code :)

[Steven Watanabe]

• I don't know what 1.5.8 is. There is a 1.58.0, though.
• I can't reproduce the problem, and I don't see any problems in the source either. The exit status appears to be propagated correctly. It should return 0 if all targets were successfully built and 1 otherwise. Our regression tests absolutely depend on this, too.