RE: g++ 4 & MACOSX_DEPLOYMENT_TARGET=10.2
RE: g++ 4 & MACOSX_DEPLOYMENT_TARGET=10.2
- Subject: RE: g++ 4 & MACOSX_DEPLOYMENT_TARGET=10.2
- From: "Nathan Herring" <email@hidden>
- Date: Wed, 16 Nov 2005 08:21:38 -0800
- Thread-topic: g++ 4 & MACOSX_DEPLOYMENT_TARGET=10.2
Would it be unreasonable to request that g++ 4.0 have a link error in
the case where MACOSX_DEPLOYMENT_TARGET=10.2 (i.e., -static-libgcc is
implicitly required but the static libgcc doesn't exist)?
I have the same source building fine under 3.3, and all is well. Thanks
for the info.
-nh
-----Original Message-----
From: Chris Espinosa [mailto:email@hidden]
Sent: Wednesday, November 16, 2005 8:14 AM
To: Nathan Herring
Cc: email@hidden
Subject: Re: g++ 4 & MACOSX_DEPLOYMENT_TARGET=10.2
On Nov 16, 2005, at 6:29 AM, Nathan Herring wrote:
> Am I correct in thinking that g++ 4-built targets won't run on 10.2?
> 10.2 doesn't have the dynamic version of the stdc++ library, just the
> static version. But, even if you want to link with -static-libgcc, the
> option is ignored in g++ 4 on 10.4.3 with the Xcode 2.2 update since
> there is no static version. No warnings or anything.
>
> Would using the 10.2 SDK make this work correctly (since a static
> version _does_ live there)? Unfortunately, since I'm using a jam
> target,
> I'm not so sure how to set it up. (Regular Xcode projects are a cinch
> that way.)
No, gcc4.0 requires the dynamic libstdc++.dylib which is only deployed
on 10.3.9 and later. To build for 10.2, use the SDK in conjunction
with gcc 3.3. You can use the GCC_VERSION = 3.3 build setting to
select this on a per-target basis (or GCC_VERSION_ppc for per-target,
per-architecture).
Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden