David and Phillip -<br><br>Thanks for the responses.<br><br>I obviously made a blunder and didn't use: bjam "-sTOOLS=darwin".<br><br>One thing I noticed was compiling the hello world for debug works using: bjam <br><br>That threw me off, when I did a: bjam release<br><br>Is there a requirement to have python installed when building boost proper? I noticed 6 targets failed related to the unit testing and wondered if they were related to python. <br><br>Best regards,<br>Aaron R><br><br><div><span class="gmail_quote">On 4/19/07, <b class="gmail_sendername">Phillip Seaver</b> <<a href="mailto:phil@apago.com">phil@apago.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> David Abrahams wrote, on 4/19/2007 4:12 AM:<br>> on Thu Apr 19 2007, Phillip Seaver <phil-AT-apago.com> wrote:<br>><br>><br>>> Based on the output directory, it looks like you're doing "using gcc <br>>> ..." when you need to do "using darwin ...".<br>>><br>><br>> How many times do people need to make this mistake before we recognize<br>> that gcc should refer to the apple compiler by default, on MacOS X? <br>><br><br>It looks like gcc.jam has enough other platform-specific code in it<br>these days to justify moving the OS X support into there. I'll try to<br>find some time to do it, unless someone more qualified wants to. :-) <br><br>I probably won't be able to get to it for the next week or so, but it<br>fits in with my long-term plans to make a toolset for OS X that handles<br>SDK's, universal binaries, target OS version, application bundles, etc. <br><br>Phillip<br>_______________________________________________<br>Unsubscribe & other changes: <a href="http://lists.boost.org/mailman/listinfo.cgi/boost-build">http://lists.boost.org/mailman/listinfo.cgi/boost-build </a><br></blockquote></div><br>