Re: [Fink-devel] Re: X11 install_name fixer script
This is handled if you install the X11 for Mac OS X SDK; the SDK is listed as a requirement in Fink's FAQ. No it isn't. Yes it is. From http://fink.sourceforge.net/doc/x11/inst-xfree86.php#apple-binary : [...] then install Apple's X11 and X11 SDK [...] Huh? No, the SDK package does not fix the install_names of apple's libraries. They are definitely broken (unless apple released a fixed version of their pkg, which i haven't heard about) Before I installed the SDK, system-xfree86 wouldn't install because of missing/mis-named/mis-linked libraries. After installing the SDK, I had said libraries linked, and system-xfree86 installed just fine. (No other X11 was present on this system; only Apple's.) Regards, Dave Schroeder University of Wisconsin - Madison --- This SF.NET email is sponsored by: Thawte.com Understand how to protect your customers personal information by implementing SSL on your Apache Web Server. Click here to get our FREE Thawte Apache Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Re: X11 install_name fixer script
At 7:47 Uhr -0600 16.01.2003, Dave Schroeder wrote: This is handled if you install the X11 for Mac OS X SDK; the SDK is listed as a requirement in Fink's FAQ. No it isn't. Yes it is. From http://fink.sourceforge.net/doc/x11/inst-xfree86.php#apple-binary : [...] then install Apple's X11 and X11 SDK [...] That's not relevant to the point Ben was making, though. Huh? No, the SDK package does not fix the install_names of apple's libraries. They are definitely broken (unless apple released a fixed version of their pkg, which i haven't heard about) Before I installed the SDK, system-xfree86 wouldn't install because of missing/mis-named/mis-linked libraries. Of course not, we know that well. After installing the SDK, I had said libraries linked, and system-xfree86 installed just fine. (No other X11 was present on this system; only Apple's.) True. But still, it's not the point Ben was making :-) He was talking about the install_name field which is *inside* the .dylibs. Max -- --- Max Horn Software Developer --- This SF.NET email is sponsored by: Thawte.com Understand how to protect your customers personal information by implementing SSL on your Apache Web Server. Click here to get our FREE Thawte Apache Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Re: X11 install_name fixer script
On Wednesday, January 15, 2003, at 09:01 PM, Dave Schroeder wrote: This is handled if you install the X11 for Mac OS X SDK; the SDK is listed as a requirement in Fink's FAQ. See: http://fink.sourceforge.net/doc/x11/inst-xfree86.php#apple-binary No it isn't. Apple's X11 is improperly linked (already a known issue -- but still broken in the current beta). Libraries have an install_name that points to the *full* name of the file, instead of the compatibility name (ie, libX11.6.2.dylib instead of libX11.6.dylib) so when libX11 changes to 6.3, any libraries or binaries that linked against the old version will break. This script edits the libraries so that they have a correct install_name. --- This SF.NET email is sponsored by: A Thawte Code Signing Certificate is essential in establishing user confidence by providing assurance of authenticity and code integrity. Download our Free Code Signing guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
