Boost logo

Boost :

Subject: [boost] Fwd: linking on OSX
From: David M. Cotter (me_at_[hidden])
Date: 2009-10-21 01:35:30

seems that when i build now (whether with the cmd that worked before,
OR if i add the cpusubtype_ALL flag), it always fails:

...found 20863 targets...
...updating 274 targets...
darwin.compile.c++.pch bin.v2/libs/math/build/darwin-4.2.1/release/
lipo: can't figure out the architecture type of: /var/folders/h7/

     "g++" -x c++-header -O3 -finline-functions -Wno-inline -Wall -
mmacosx-version-min=10.4 -dynamic -no-cpp-precomp -gdwarf-2 -arch i386
DBOOST_MATH_TR1_DYN_LINK=1 -DNDEBUG -I"." -I"libs/math/src/tr1" -c -o
macosx-version-min-10.4/threading-multi/../src/tr1/pch.hpp.gch" "libs/

...failed darwin.compile.c++.pch bin.v2/libs/math/build/darwin-4.2.1/
...skipped <pbin.v2/libs/math/build/darwin-4.2.1/release/architecture-
combined/macosx-version-min-10.4/threading-multi>assoc_laguerre.o for
lack of <pbin.v2/libs/math/build/darwin-4.2.1/release/architecture-
...<a bunch more like above>
...failed updating 4 targets...
...skipped 270 targets...

so it's not building at all. why is it now skipping all targets?
sorry i'm kindof a n00b at this

> well, no i meant bjam
> is "" another name for "bjam" ??
> this is what i use to build boost right now:
> > ./bjam macosx-version-min=10.4 architecture=combined install
> so are you saying i can do this?
> > ./bjam macosx-version-min=10.4 architecture=combined linkflags="-
> force_cpusubtype_ALL" install
> ?
> On Oct 20, 2009, at 10:10 PM, Vladimir Prus wrote:
>> David M. Cotter wrote:
>>> from Chris again:
>>>> Just to follow up on this: there appears to be some odd (or at
>>>> least
>>>> non-obvious) behaviour with the linker in Xcode 3.2. If you set the
>>>> deployment target to 10.3, the resulting architecture ends up as
>>>> ppc7400 whereas 10.4 will give you ppc. (10.5 and 10.6 give you
>>>> ppc7400.)
>>>> Anyway, if you know your code will work on all PowerPC CPU
>>>> subtypes,
>>>> it looks like you could use the -force_cpusubtype_ALL linker flag
>>>> (I
>>>> haven't tried it).
>>> again: how do i do this using bjam?
>> I think you meant "using Boost.Build". There are cflags and
>> linkflags properties
>> that you can specify on the command line. E.g.
>> linkflags="-force_cpusubtype_ALL"
>> Does this help?
>> - Volodya

Boost list run by bdawes at, gregod at, cpdaniel at, john at