Re: ld -syslibroot reliability
Re: ld -syslibroot reliability
- Subject: Re: ld -syslibroot reliability
- From: Daniel Jalkut <email@hidden>
- Date: Tue, 2 Jan 2007 15:24:15 -0500
Eric set me straight about the functionality of ld ... my problems
were based in some erroneous full-path references to system
libraries, provided on the command line to ld. I guess these lead
ld's search mechanism out of my SDK, allowing it to register some
libraries explicitly by full path before locating them in the SDK by
implicitly resolving -l and -framework options.
Sorry for the false alarm...
Daniel
On Jan 2, 2007, at 2:09 PM, Eric Albert wrote:
On Jan 2, 2007, at 10:40 AM, Daniel Jalkut wrote:
I've observed some pretty funky behavior with ld's dylib
resolution process, and found at least one bug in the way it tries
to fix-up dylib references with -syslibroot:
http://www.red-sweater.com/blog/246/missing-link
If any Apple engineers who are familiar with ld get a chance to
look at it, I'd be interested to hear your feedback.
Unfortunately my observations are a little vague because I'm still
sort of wrapping my head around the problem. But I did report a
bug # 4904317.
To be able to diagnose this I think we'd need to see the full link
line. Can you send that along or attach it to the bug?
-Eric
_______________________________________________
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