This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: issues with configuring the trunk to build Fortran
- From: Andrew Pinski <pinskia at physics dot uc dot edu>
- To: gerald at pfeifer dot com (Gerald Pfeifer)
- Cc: pinskia at physics dot uc dot edu (Andrew Pinski), Joe dot Buck at synopsys dot COM (Joe Buck), gcc at gcc dot gnu dot org
- Date: Wed, 25 Aug 2004 17:30:35 -0400 (EDT)
- Subject: Re: issues with configuring the trunk to build Fortran
>
> On Wed, 25 Aug 2004, Andrew Pinski wrote:
> > Should people read the installation instructions?
>
> I agree that people should read our instruncions, however that should
> _not_ prevent us from improving our diagnostics and failure messages.
>
> > Well this is the reason why we get so many reports about using
> > sh in Solaris.
> >
> > http://gcc.gnu.org/install/prerequisites.html
>
> Both in the example that Joe reported and, in fact, the Solaris sh
> issue, this shouldn't be too hard for someone in the respective code.
>
> There is something beyond the bug versus non-bug/read-the-docs
> distinction, which is quality of implementation. And I'm tempted
> to think that whenever someone experienced like Joe trips over a
> usability issue, we should take that very seriously.
OK what about the binutils requirment for x86-linux and cctools
requirment for Darwin, these seem like things which should be documented
but not forced as we don't know really unless we do a huge complex test
that the requirement is met.
-- Pinski
>
> Gerald
>
>