Re: Target library disabling at toplevel

"Joseph S. Myers" <[email protected]> writes:
> (And why (CC to maintainer) do some CRIS and MMIX targets list Fortran
> in unsupported languages?  I didn't think the Fortran libraries had
> any porting issues, unlike Java and Go and Ada.)

For the record, builds with mipsisa64-elf fail with:

libgfortran/intrinsics/time_1.h:99:1: error: static declaration of ‘localtime_r’ follows non-static declaration
newlib/libc/include/time.h:61:12: note: previous declaration of ‘localtime_r’ was here

This is a long-standing problem.  It got stalled a while ago because of
a disagreement (in my eyes anyway) about how libgloss targets should be
handled.  We started down the path of using -T<target>.ld, so that they
could be treated like other targets.  But I preferred (and still prefer)
the idea of making libgfortran handle newlib in the same way as libstdc++,
or disabling libgfortran if we don't care.  I think Rask Ingemann
Lambertsen also had a patch that used a config.cache-style approach.

Richard