I think I got it with Snow Leopard and 32_64. First, looking at the lines with &quot;arch-addr-flags&quot;, I realized what I really needed was architecture=x86 address-model=32_64 instead of architecture=combined address-model=32_64 (I needed Intel-only binaries, but I tested this also works for architecture=combined if you remove the -arch ppc64 from tools/darwin.jam:307-317). This removed the unfound bits/* headers error, but created a new one:<div>
<br></div><div><div>darwin.compile.c++ bin.v2/libs/iostreams/build/darwin-4.2.1/release/address-model-32_64/architecture-x86/threading-multi/file_descriptor.o</div><div><br></div><div>    &quot;g++&quot;  -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -dynamic -no-cpp-precomp -gdwarf-2 -arch i386 -arch x86_64 -fPIC -m64  -DBOOST_ALL_NO_LIB=1 -DBOOST_IOSTREAMS_DYN_LINK=1 -DNDEBUG  -I&quot;.&quot; -c -o &quot;bin.v2/libs/iostreams/build/darwin-4.2.1/release/address-model-32_64/architecture-x86/threading-multi/file_descriptor.o&quot; &quot;libs/iostreams/src/file_descriptor.cpp&quot;</div>
<div><br></div><div>lipo: /var/folders/hh/hh89RPWHGkKJgJC3Gy-ZZk+++TI/-Tmp-//ccXdF5pl.out and /var/folders/hh/hh89RPWHGkKJgJC3Gy-ZZk+++TI/-Tmp-//ccg03e1J.out have the same architectures (x86_64) and can&#39;t be in the same fat output file</div>
<div>...failed darwin.compile.c++ bin.v2/libs/iostreams/build/darwin-4.2.1/release/address-model-32_64/architecture-x86/threading-multi/file_descriptor.o...</div><div><br></div><div>I tried the same g++ command-line, but with &quot;-m64&quot; removed, and it worked and created the proper fat object file:</div>
<div><br></div><div><div>$ lipo -info bin.v2/libs/iostreams/build/darwin-4.2.1/release/address-model-32_64/architecture-x86/threading-multi/file_descriptor.o </div><div>Architectures in the fat file: bin.v2/libs/iostreams/build/darwin-4.2.1/release/address-model-32_64/architecture-x86/threading-multi/file_descriptor.o are: i386 x86_64</div>
<div><br></div><div>I found that -m64 is being set in tools/gcc.jam based on the address-model at around line 377. So I added a check whether the model is 32_64, and add -m64 only if 32 is not set *and* 32_64 is not set:</div>
<div><br></div><div><div>            if $(model) = 32</div><div>            {</div><div>                option = -m32 ;</div><div>            }</div><div>            else</div><div>            {</div><div>                if $(model) = 32_64</div>
<div>                {</div><div>                }</div><div>                else</div><div>                {</div><div>                    option = -m64 ;</div><div>                }</div><div>            }</div><div><br>
</div></div></div><div>Then I compiled with architecture=x86 address-model=32_64 and got universal binaries as I needed:</div><div><br></div><div>$ lipo -info lib/libboost_iostreams-xgcc42-mt.dylib </div><div>Architectures in the fat file: lib/libboost_iostreams-xgcc42-mt.dylib are: i386 ppc7400 x86_64</div>
<div><br></div><div>$ lipo -info lib/libboost_iostreams-xgcc42-mt-1_40.dylib</div><div>Architectures in the fat file: lib/libboost_iostreams-xgcc42-mt-1_40.dylib are: i386 x86_64</div><div><br></div><div>I also tried architecture=combined address-model=32_64 (after I removed -arch ppc64 from tools/darwin.jam), and confirmed that again, the &quot;-m64&quot; is what causes errors (I tested that it somehow forces 64-bit even if you previously specify 32-bit arch(s) with -arch option). With the same fix for -m64, this works:</div>
<div><br></div><div><br></div><div><br></div><div>In my opinion, more proper would be to:</div><div><br></div><div>1. in tools/gcc.jam:(352-383), if the toolset is darwin, don&#39;t setup address-model flags (-m32 and -m64), since these are taken care of in tools/darwin.jam (and in a correct way specific for Apple&#39;s gcc).</div>
<div>2. in tools/darwin.jam:(307-317), somehow check for the version of SDK (or version of OS X, don&#39;t know which one is more correct) and based on that, handle the unavailable -arch ppc64.</div><div><br></div><div>On a side note, I hope boost.build will soon be in Python, which I know well, since then I am willing to learn Boost.Build and submit proper patches without hacks :-)</div>
<div><br></div><div>Cheers,</div><div>Boris</div><br><div class="gmail_quote">On Sun, Sep 6, 2009 at 2:34 AM, JungleCat <span dir="ltr">&lt;<a href="mailto:junglecat@orchidseed.org">junglecat@orchidseed.org</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div style="word-wrap:break-word">ok, the problem is that you cannot compile c++ into ppc64 machine code on Snow Leopard because it doesn&#39;t ship with a ppc64 bit version of the SDK.<div>
<br></div><div>The following is the culprit in darwin.jam</div><div><br></div><div>arch-addr-flags darwin OPTIONS : combined : 64 : -arch x86_64 <b>-arch ppc64 </b>;</div><div><br></div><div>My last post demonstrated the failure but you cannot build through Xcode because it will bail with the same error. My take is that Apple is dropping support for ppc64 but I have no confirmation other than they do not ship the ability to target this anymore.</div>
<div><br></div><div>Julian</div><div><br></div></div></blockquote></div></div>