Martin,
I agree. I do not hold the X11 developers as being responsible
for the linker bug itself. However, they are responsible for not
exposing the problem with the new linker and X11 until very
late in development of Leopard. At this point, my main concern is
that (unlike System Updates), I am unaware of any mechanism by
which Apple beta-tests Xcode developer updates (short of Preview
releases). Specifically, currently Leopard can't link libGLw even
with the proposed framework libGL hack. It is unclear is this is
a side-effect of the framework libGL hack or an entirely separate
bug. My fear is that we may have the cyclic linkage issue fixed
in the first Xcode developer update only to find that there are
remaining bugs like libGLw that are unaddressed. The libGLw bug
is particularly problematic since it requires Motif to be installed
in order to build a test case which will likely inhibit Apple from
testing this internally.
Jack
On Tue, Nov 06, 2007 at 10:50:25AM +0100, Martin Costabel wrote:
>
> This is definitely not the fault of X11.
>
> --
> 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
[email protected]
http://news.gmane.org/gmane.os.apple.fink.devel
