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: gfortran test runs

From: Scott Robert Ladd <coyote at coyotegulch dot com>
To: gcc mailing list <gcc at gcc dot gnu dot org>
Date: Wed, 25 Aug 2004 13:37:57 -0400
Subject: Re: gfortran test runs
References: <1093439260.5415.1257.camel@p4> <20040825134546.GA26416@nevyn.them.org> <1093442437.13982.1335.camel@p4> <1093448278.22129.21.camel@pc960.cambridge.arm.com>

Richard Earnshaw wrote:

It really shouldn't be necessary for gcc developers to have to install
components into /usr/lib (or any other system directory) in order to be
able to develop and test the compiler.

I think the current situation is seriously broken and needs to be
addressed urgently.


I'll second your opinion. This dependency will be an impediment to the
adoption of GCC 3.5 and gfortran, if for no other reason than creating
frustration. Granted, GCC has other requirements -- but GMP is a
somewhat unusual requirement that lies outside most standard installs.

--
Scott Robert Ladd
Coyote Gulch Productions (http://www.coyotegulch.com)
Software Invention for High-Performance Computing

References:
- gfortran test runs
  - From: Andrew MacLeod
- Re: gfortran test runs
  - From: Daniel Jacobowitz
- Re: gfortran test runs
  - From: Andrew MacLeod
- Re: gfortran test runs
  - From: Richard Earnshaw

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