LD_PREBIND and LD_PREBIND_ALLOW_OVERLAP harmful on 10.5

[mww@…]

Setting LD_PREBIND and LD_PREBIND_ALLOW_OVERLAP to "1" results in build errors on various ports in Mac OS X 10.5 which fail with ld: symbol(s) not found ...; e.g. the postgresql ports fail to compile (#12994)

Could we remove this feature for the 1.6 release? (or make it OS dependant or configurable? Does it make sense on 10.5 at all?)

[pguyot (Paul Guyot)]

I'm wondering why I'm the owner of this bug. Judging from the style of the comment, I don't think I'm the one who put that in...

Anyway. Prebinding is useless on 10.4 and while we have issues with 10.5, I am a definitive supporter of the "current release + previous release" support and therefore would advocate removing all remainings of the LD_PREBIND stuff. I can put a .diff here if this helps, or commit the thing myself.

[tcollen@…]

just adding a note so i can watch this ticket.

[mww@…]

Replying to pguyot@kallisys.net:

I'm wondering why I'm the owner of this bug. Judging from the style of the comment, I don't think I'm the one who put that in...

Sorry - I had the impression from the logfiles that you put that in initially.

Anyway. Prebinding is useless on 10.4 and while we have issues with 10.5, I am a definitive supporter of the "current release + previous release" support and therefore would advocate removing all remainings of the LD_PREBIND stuff. I can put a .diff here if this helps, or commit the thing myself.

Either way would be fine for me -- I'd just like to have it out for v1.6! Thanks!

[mww@…]

I've removed both environment variables from macports.tcl -- this seemed to be the only place where they were used. (commit 31786)

[jmpp@…]

Does prebinding have any meaning on 10.3? If so, maybe a simple if to keep the needed environment on that platform would be a nicer approach...

Other than that, this is certainly a merger candidate for the 1.6 branch. I'll work on it once I get some 10.3 feedback, thanks!

-jmpp