This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: multilibbing libgfortran

From: Nathanael Nerode <neroden at twcny dot rr dot com>
To: Andreas Jaeger <aj at suse dot de>
Cc: gcc at gcc dot gnu dot org
Date: Sun, 03 Aug 2003 12:52:06 -0400
Subject: Re: multilibbing libgfortran
References: <3F2D20A5.9000708@twcny.rr.com> <u8y8ya4wv4.fsf@gromit.moeb>

Andreas Jaeger wrote:

Nathanael Nerode <neroden@twcny.rr.com> writes:


Unfortunately exact enough - but too late.  I'd prefer to have
libgfortran earlier multi-libbed if possible so that it can get better
tested.

So, what needs to be done to get this multi-libbed?  I tried copying
some stuff from libstdc++-v3 and failed with automake problems :-(

Andreas

The current multilibbing scheme is demented, in my opinion. I still recommend not multilibbing at the moment; when multilibbing is moved to the top level, you'll have to rip all the multilib code back *out* of gfortran. You can still test gfortran with each individual library configuration directly, you know, right?

Follow-Ups:
- Re: multilibbing libgfortran
  - From: Andreas Jaeger

References:
- Re: multilibbing libgfortran
  - From: Nathanael Nerode
- Re: multilibbing libgfortran
  - From: Andreas Jaeger

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]