This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Target library disabling at toplevel
- From: Richard Sandiford <richard dot sandiford at linaro dot org>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: gcc at gcc dot gnu dot org, java at gcc dot gnu dot org, hp at axis dot com, hp at bitrange dot com
- Date: Wed, 23 Mar 2011 11:24:17 +0000
- Subject: Re: Target library disabling at toplevel
- References: <Pine.LNX.4.64.1103221942200.9686@digraph.polyomino.org.uk>
"Joseph S. Myers" <joseph@codesourcery.com> 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