Steve,
That comment isn't quite fair. Currently on MacOS X
10.4.8, we only have 32 failures for both -m32 and -m64
in the fortran testsuite. Three quarters of those are
definitely due to the problem with the long double
system calls not being mapped and the other ones
(due to isfinite breakage) may be related as well
since it only happens with long doubles.
Bradley tends to push the envelope by using
non-standard flags in his build plus he is using
the newly added powerpc64-*-darwin* target instead
of powerpc-*-darwin*. Perhaps it would help if
Bradley repeated his build without the -mcpu=970
to see if that eliminates the problems. Also I
assume Bradley remembered to install the build
before running make check. I see lots of libgomp
failures I believe those could be due to that.
Also, Bradley, did you remember to patch the
prune.exp scripts in the testsuite? You will
get a huge number of false failures due to
linker warnings at -m64 with -g if you don't.
Jack
On Wed, Dec 06, 2006 at 10:24:33AM -0800, Steve Kargl wrote:
>
> Can you make testsuite/gfortran/gfortran.log available?
> I suspect that this is yet another Darwin is a broken
> OS problem.
>
> Have you ever thought about replacing darwin with something
> that actually is functional?
>
> --
> Steve
>
