To avoid random starting segment addresses I think that gcc-prebind utility might help. One could use gcc-prebind to build these libs, capture the build output and then hopefully come up with a "static" address and patch so fink can build them normally (without this utility).
Carsten
On Tuesday, February 11, 2003, at 10:52 am, Ben Hines wrote:
Folks with fileutils and various other fink packages installed are harassed by thousands of prebinding warnings:
Feb 11 07:44:07 G4 /usr/libexec/fix_prebinding: /sw/bin/cut could not be launched prebound.
Feb 11 07:44:07 G4 /usr/libexec/fix_prebinding: /sw/bin/cut couldn't be prebound in the past, and probably can't be prebound now.
Feb 11 07:44:07 G4 /usr/libexec/fix_prebinding: 2003-02-11 07:44:07 -0800: prebinding for cut done.
Feb 11 07:44:16 G4 /usr/libexec/fix_prebinding: /sw/bin/find could not be launched prebound.
Feb 11 07:44:16 G4 /usr/libexec/fix_prebinding: /sw/bin/find couldn't be prebound in the past, and probably can't be prebound now.
dyld: ls: prebinding disabled because library: /sw/lib/libintl.1.dylib got slid
Until we come up with a full prebinding database, I suggest we patch the gettext and libiconv packages to prebind libintl and libiconv dylibs, specifying random seg1addrs. It might not always work, but it will be better than the present "will NEVER work" situation. If another library conflicts, itll just fail to prebind. No big deal.
Obviously this will only help for things that use only gettext and libiconv libraries, but there are quite a lot of apps in fink that only use those. :) (Along with everything in fileutils, others include stuff like, dpkg-split, dpkg-deb, gtar...)
Objections... ?
-Ben
------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
