• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Link errors
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Link errors


  • Subject: Re: Link errors
  • From: Steve Mills <email@hidden>
  • Date: Thu, 13 Apr 2006 11:16:54 -0500

On Apr 13, 2006, at 01:14, Eric Albert wrote:

I think Chris suggested that due to the 'ld64' above. ld64 is the linker for ppc64. But the message above references a module in Libsystem, not a binary. And there is a module called ld64.o in Libsystem, as you can see by doing
nm /usr/lib/libSystem.B.dylib | grep ld64
on any Panther or Tiger system. ld64.o comes from ld64.c in Libm and contains implementations of long double APIs which use doubles instead of long double for folks who build with -mlong-double-64 to get 64-bit long doubles (which we don't recommend).


Instead, something here is causing you to pull in the system's Libsystem rather than the SDK's. One way to try to find it would be to look through the entire build transcript for the first reference to /usr/lib/libSystem.B.dylib and see if that shows you anything. Another option is to open your real project file -- the project.pbxproj inside the package that is your project -- in a text editor and look for any explicit references to /usr/lib/ libSystem.B.dylib. Those should theoretically all get turned into SDK references automatically, but it sounds like you might've found a case where that doesn't happen....

I've cleaned and built all the subprojects and none of their transcripts contains libSystem at all. I've also checked the project.pbxproj files for each and libSystem is in none of them. I'm now doing a full clean and build on the main project and the subprojects and will check the transcript. The only thing I've found that might be wrong and I don't understand is that one project that builds a PDE had the header search paths and framework search paths set to "$(NEXT_ROOT)/System/Library/Frameworks/Some.framework". I can't find mention of NEXT_ROOT in the documentation, so I don't know what it means, but I've change all those to $(SDKROOT)/blah. Anybody know if NEXT_ROOT is still a compiler macro (or whatever they're called)?


Steve Mills
Drummer, Mac geek
http://sjmills5.home.mchsi.com/


_______________________________________________ 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
References: 
 >Link errors (From: Steve Mills <email@hidden>)
 >Re: Link errors (From: Chris Espinosa <email@hidden>)
 >Re: Link errors (From: Eric Albert <email@hidden>)

  • Prev by Date: Re: Help : Compiling for multiple architectures, is ppc970 valid ?
  • Next by Date: Re: Link errors
  • Previous by thread: Re: Link errors
  • Next by thread: Re: Link errors
  • Index(es):
    • Date
    • Thread