https://svn.boost.org/trac10/ticket/4147 <p> In many of the Jamfiles in Boost, the "os" property is used to add libraries and defines appropriate to the target operating system. But the "os" property doesn't give the target operating system; it gives the build operating system. The "target-os" property gives the target operating system. So these Jamfiles do the wrong thing when cross-compiling. </p> <p> According to Vladimir Prus on the Boost-build mailing list: </p> <p> "Yes, in most cases 'target-os' should be used. Please file bugs for libraries that use 'os'." </p> <p> The full list of Boost libraries that appear to have this problem is: </p> <p> asio iostreams thread </p> <p> I generated this list by doing "grep 'import os'" and filtering out the python files, so it may not be all that accurate. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/4147 Trac 1.4.3 anonymous Mon, 07 Jun 2010 09:50:21 GMT https://svn.boost.org/trac10/ticket/4147#comment:1 https://svn.boost.org/trac10/ticket/4147#comment:1 <ul> <li><strong>owner</strong> set to <span class="trac-author">Vladimir Prus</span> </li> <li><strong>component</strong> <span class="trac-field-old">Building Boost</span> → <span class="trac-field-new">build</span> </li> </ul> <p> Merge Building Boost with build tool. </p> Ticket