This is the mail archive of the
mailing list for the GCC project.
Re: [toplevel, gfortran] Support --disable-libgfortran option
- From: Hans-Peter Nilsson <hp at bitrange dot com>
- To: Kelley Cook <kcook at gcc dot gnu dot org>
- Cc: gcc-patches at gcc dot gnu dot org, fortran at gcc dot gnu dot org
- Date: Mon, 8 Nov 2004 17:33:00 -0500 (EST)
- Subject: Re: [toplevel, gfortran] Support --disable-libgfortran option
- References: <418FCCE4.firstname.lastname@example.org>
On Mon, 8 Nov 2004, Kelley Cook wrote:
> HP's patch (http://gcc.gnu.org/ml/gcc-patches/2004-11/msg00572.html) to
> disable libgfortran on mmix and some other complaints about libgfortran
> on cross targets led to me to write this patch which correctly adds in a
> --disable-libgfortran option.
> It also moves the logic for disabling libgfortran on mmix into this
> option which means that a mmix user could --enable-libgfortran, if they
> wished. (It defaults to not using it on that target)
When you test them, you'll find that all *-*-*elf and
*-*-eabi* should have it disabled by default too.
But better is to fix libgfortran, of course.
> ./configure --target=mmix-unknown-elf (no)
For the record, there's no mmix-unknown-elf, though that doesn't
affect the validity of your testing.