• 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: libSystem and CoreFoundation conflict?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: libSystem and CoreFoundation conflict?


  • Subject: Re: libSystem and CoreFoundation conflict?
  • From: Daniel Hazelbaker <email@hidden>
  • Date: Wed, 4 May 2005 13:21:29 -0700

Just tried that and did a full recompile and got the same results. Is there a way to look at this prebinding address information in the files so I can compare with a clean 10.4 machine?

Daniel

On May 4, 2005, at 12:53 PM, Jim Ingham wrote:

Somehow, the prebinding on your system didn't get updated when you installed.

Try (in Terminal):

  sudo update_prebinding -force


Jim

On May 4, 2005, at 11:32 AM, Daniel Hazelbaker wrote:


Greetings,

I have a project that has been around since Project Builder. I just upgraded to Tiger and XCode 2.0 and am now suddenly getting link warnings that do not make sense. I am used to my own frameworks and libraries conflicting with apple's when I forget to change the base address, but after the upgrade it seems that libSystem and CoreFoundation are conflicting.

/usr/bin/ld: warning prebinding disabled because (__TEXT segment (address = 0x90000000 size = 0x1a7000) of /usr/lib/ libSystem.B.dylib overlaps with __TEXT segment (address = 0x90190000 size = 0xae000) of /System/Library/Frameworks/ CoreFoundation.framework/Versions/A/CoreFoundation
/usr/bin/ld: warning prebinding not disabled even though (__LINKEDIT segment (address = 0x901a7000 size = 0x56764) of /usr/ lib/libSystem.B.dylib overlaps with __TEXT segment (address = 0x90190000 size = 0xae000) of /System/Library/Frameworks/ CoreFoundation.framework/Versions/A/CoreFoundation on the assumption that the stripped output will not overlap
/usr/bin/ld: warning prebinding disabled because (__TEXT segment (address = 0x90000000 size = 0x1a7000) of /usr/lib/ libSystem.B.dylib overlaps with __TEXT segment (address = 0x90190000 size = 0xae000) of /System/Library/Frameworks/ CoreFoundation.framework/Versions/A/CoreFoundation
/usr/bin/ld: warning prebinding not disabled even though (__LINKEDIT segment (address = 0x901a7000 size = 0x56764) of /usr/ lib/libSystem.B.dylib overlaps with __TEXT segment (address = 0x90190000 size = 0xae000) of /System/Library/Frameworks/ CoreFoundation.framework/Versions/A/CoreFoundation on the assumption that the stripped output will not overlap


I've never before had apple's system libraries have problems. If it helps, a few days before installing Tiger, I updated to 10.3.9 and then did an upgrade to 10.4, not a clean install (in the middle of school, don't have time right now).

Anybody seen this before?

Daniel Hazelbaker
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com


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
References: 
 >libSystem and CoreFoundation conflict? (From: Daniel Hazelbaker <email@hidden>)
 >Re: libSystem and CoreFoundation conflict? (From: Jim Ingham <email@hidden>)

  • Prev by Date: Re: Best practices for upgrading?
  • Next by Date: Best way to get Darwin Source references to work in Xcode 2?
  • Previous by thread: Re: libSystem and CoreFoundation conflict?
  • Next by thread: Best practices for upgrading?
  • Index(es):
    • Date
    • Thread