David,
Thanks for the clarification. While one could argue that the breakage was
due to an aggressive introduction of changes into gfortran of the gcc 4.1
branch,
it is definitely is more honest to say that the Darwin target has been broken
for sometime now with the weakref failures in the gcc
> Jack Howarth writes:
Jack> My question is whether the gcc 4.1 release would be
Jack> held to fix this or will the Darwin target just be marked as broken for
Jack> that release?
The release will be held. Quoting the GCC development plan:
"If ... support for a platform with active m
In case folks haven't noticed, there has been major breakage of
the gfortran in gcc 4.1 on Darwin. The problem appears to be due to
the fact that weakrefs aren't properly honored in the Darwin linker.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24991
This apparently is the same issue causin
