Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: OpenAL & prebinding warnings

On Thursday, September 26, 2002, at 01:49 AM, Chris Hanson wrote:

This is true, however, here is a point from the ld man page:

-prebind_allow_overlap

This is insane! If it's possible to do this, WHY ISN'T IT THE DEFAULT?


I think insane is a bit strong. In any case, more investigations reveal that libtool does not understand "-prebind_allow_overlap" and so will not pass this through to ld during the build process.

And I was correct in my conjecture before: trying to use -seg1addr 0x90000000 conflicts with current locations of Apple frameworks. In my test, the pre-loaded System libraries occupy from (starting addresses) 0x872b0000 (a printer lib) to 0x93ec0000 (web services).

The other space given as free in the 10.1 prebinding release notes, (0x00000000 to 0x3FFFFFFF), become occupied by the executable, the non-Apple library in question (Quesa, in this example), and some OpenGL components: GLProfiler, GLEngine, etc. (the OpenGL *framework* is amongst the System frameworks). I don't think that contradicts. So the library could be prebound at the seg1addr starting 0x3FFFFFFF less its size.

The problem is that if the library isn't prebound, then the application cannot be.

Can someone tell me how pre-binding works if the locations of the pre-bound libraries change?

--
Brent
_______________________________________________
mac-games-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/mac-games-dev
Do not post admin requests to the list. They will be ignored.
References: 
 >Re: OpenAL & prebinding warnings (From: Chris Hanson <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.