Re: Can gcc 4 built binaries be used on 10.2 to 10.3.8? (undefined reference to _fprintf$LDBL128 expected to be defined in /usr/lib/libSystem.B.dylib)
Re: Can gcc 4 built binaries be used on 10.2 to 10.3.8? (undefined reference to _fprintf$LDBL128 expected to be defined in /usr/lib/libSystem.B.dylib)
- Subject: Re: Can gcc 4 built binaries be used on 10.2 to 10.3.8? (undefined reference to _fprintf$LDBL128 expected to be defined in /usr/lib/libSystem.B.dylib)
- From: David Young <email@hidden>
- Date: Thu, 1 Dec 2005 15:47:24 -0800
This isn't entirely the same thing, as using GCC_VERSION_ppc gets you
gcc 3.3 for PowerPC and 4.0 for Intel.
If the original poster is dead set on 4.0 for both, he/she may have
some luck with the process detailed here:
http://www.stuffonfire.com/2005/10/one_halfbaked_idea_and_one_use.html
--dave
On Dec 1, 2005, at 3:37 PM, Lawrence Gold wrote:
On Dec 1, 2005, at 4:00 PM, E. Wing wrote:
Setting the DEPLOYMENT_TARGET is probably a bad idea anyway since the
Universal Binary stuff in Xcode sets it to 10.4. But we would like to
know if there is something we can do to make this just work. (Our
alternatives seem to be modifying the build system to build once for
each architecture and writing scripts to lipo the things together, or
dropping Jaguar support which seems kind of silly to lose for just
this reason.)
Adding GCC_VERSION_i386 and GCC_VERSION_ppc to your build settings
and setting them to 4.0 and 3.3 respectively will do the trick.
_______________________________________________
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
_______________________________________________
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