Martin,
This isn't quite the case here. I have been told by Apple's
programmers that these linker checks on cyclic use of libraries
has been in place for almost a year now in Xcode 3.0. This means
that had the X11 component been ported to the new linker in
a timely manner, there would have been plenty of time to address
this issue before Leopard's release. As it stands, I suspect
we won't see this issue fixed for at least six months at best.
My main concern is that we will have have an even worse solution
foisted on us without warning. I am unclear on what mechanism
Apple has for beta-testing proposed Xcode changes but it would
be really nice if someone from fink could be put in the loop
on that change (to provide feedback on the impact of previous
X11 binaries and existing X11 packages).
Jack
On Sun, Oct 28, 2007 at 10:36:52AM +0100, Martin Costabel wrote:
>
> At the release of every new version of OSX, Apple have been doing
> similar things. They always introduced some major last-minute breakage
> in the developer tools.
>
> --
> Martin
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel
