Re: [boost] linking on OSX

Subject: Re: [boost] linking on OSX
From: David M. Cotter (me_at_[hidden])
Date: 2009-10-20 23:03:45

okay we now know what the problem is, the question for the BOOST folk  
is: how do i do this with bjam?

On Oct 20, 2009, at 7:23 PM, Chris Suter wrote:

> Hi David,
>
> On Wed, Oct 21, 2009 at 1:03 PM, David M. Cotter <me_at_[hidden]>  
> wrote:
> okay.  everything is working fantastically, however, it won't run on  
> G3 machine running 10.4.11
> it works perfectly on a G4 PPC machine also running 10.4.11
>
> is there some way to "tune" bjam to emit G3-compatible code?
> cuz i'm getting this:
>
> Host Name:      TAZ-2
> Date/Time:      2009-10-20 05:56:18.099 -0700
> OS Version:     10.4.11 (Build 8S165)
> Report Version: 4
>
> Command: FooBar Pro
> Path:    /Applications/FooBar Pro.app/Contents/MacOS/FooBar Pro
> Parent:  WindowServer [310]
>
> Version: FooBar Pro 1.0d50r33 (1.0)
>
> PID:    445
> Thread: Unknown
>
> Link (dyld) error:
>
> Library not loaded: @loader_path/../SharedSupport/ 
> libboost_thread.dylib
>   Referenced from: /Applications/FooBar Pro.app/Contents/MacOS/ 
> FooBar Pro
>   Reason: no suitable image found.  Did find:
> 	/Applications/FooBar Pro.app/Contents/MacOS/../SharedSupport/ 
> libboost_thread.dylib: no matching architecture in universal wrapper
> 	/Applications/FooBar Pro.app/Contents/MacOS/../SharedSupport/ 
> libboost_thread.dylib: no matching architecture in universal wrapper
>
> This is most likely because you're only building for G4 machines and  
> greater. If you run otool -f -v <binary>, you'll probably see  
> cpusubtype set to CPU_SUBTYPE_POWERPC_7400 (which basically means G4  
> or greater).
>
> To fix, as a minimum, you need to make sure that your deployment  
> target is set to 10.4 or less and make sure your architecture  
> setting is ppc rather than ppc7400.
>
> Kind regards,
>
> Chris