Re: Pre-binding disabled/enabled warnings
Re: Pre-binding disabled/enabled warnings
- Subject: Re: Pre-binding disabled/enabled warnings
- From: Fritz Anderson <email@hidden>
- Date: Fri, 12 May 2006 10:47:52 -0500
On 11 May 2006, at 7:14 PM, Christopher Hunt wrote: Since a recent upgrade of xcode to v.2.2.1 (at least I think since then) I've been getting the following warnings for my project. They're not a problem but I'd like to understand if the warnings can be eliminated in the interests of being tidy.
I've got a basic understanding of what pre-binding is all about and I see from the below that the net effect is that pre-binding remains enabled.
... /usr/bin/ld: warning prebinding disabled because (__PAGEZERO segment (address = 0x0 size = 0x1000) of /Volumes/Users HD/Users/huntc/Development/TitanClassEnterprise/Cocoa Time Place/build/Development/World.app/Contents/MacOS/World overlaps with __TEXT segment (address = 0x0 size = 0xc000) of /usr/lib/libgcc_s.1.dylib Does the -prebind option appear in your link commands?
Double-click your product name under the Targets group, type "preb" into the search field under the Build tab, and see if Prebinding is checked. The rule of thumb, nowadays, is that it should be unchecked (there's no advantage to it on Mac OS versions 10.3.5 and up).
Interestingly, the description for the Prebinding option says This setting determines if prebinding will be attempted by adding -prebind to linker flags, and defaults to being active for all product types except static libraries. [PREBINDING]
The part about being active by default surprises me. I had thought that was no longer the case.
-- F
|
_______________________________________________
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