Nevermind, I guess I did not search hard enough and found the correct patches.<br><br><div class="gmail_quote">On Mon, Nov 1, 2010 at 1:10 PM, Jonathan Brannan <span dir="ltr">&lt;<a href="mailto:kickace@gmail.com">kickace@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div>We recently switched from boost 1.39 to boost 1.44.  We use the bjam and boost build packaged with the version of boost we use.<br>
</div><div><br></div><div>It seems that the bjam packaged with 1.44 exists with 0 even if there is a failure:</div>
<div><br></div><div>...failed gcc.compile.c++ /home/foo/Foo.o...
...failed updating 1 target...
</div><div>machine:/home/foo # echo $?</div><div>0</div><div><br></div><div>It stops early with the -q and prints out that it failed, it just exits 0.</div><div><br></div><div>bjam -v
Boost.Jam  Version 3.1.18. OS=LINUX.
   Copyright 1993-2002 Christopher Seiwald and Perforce Software, Inc.  
   Copyright 2001 David Turner.
   Copyright 2001-2004 David Abrahams.
   Copyright 2002-2008 Rene Rivera.
   Copyright 2003-2008 Vladimir Prus.
</div><div><br></div><div>With Version 3.1.17. OS=LINUX version that came with 1.39, I get an exit status of 1, which is what I expect.</div><div><br></div><div><br></div>
</blockquote></div><br>