This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Using GCC 2.95 as a bootstrap compiler
- From: Richard Earnshaw <rearnsha at arm dot com>
- To: "Joseph S. Myers" <jsm at polyomino dot org dot uk>
- Cc: Richard dot Earnshaw at arm dot com, Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>, gcc at gcc dot gnu dot org, Geoffrey Keating <geoffk at geoffk dot org>
- Date: Fri, 31 Oct 2003 11:47:02 +0000
- Subject: Re: Using GCC 2.95 as a bootstrap compiler
- Organization: ARM Ltd.
- Reply-to: Richard dot Earnshaw at arm dot com
> On Fri, 31 Oct 2003, Richard Earnshaw wrote:
>
> > I came across this the other night. It's a version skew of
> > gengtype-yacc.h between an obsolete copy in the source tree and a
> > generated copy in the build tree. gcc-2.95 was including the files in a
> > different order based on #line directives[1].
>
> Perhaps we should remove most or all of the .cvsignore files in the source
> tree, to draw people's attention to the obsolete generated files left
> behind there (and potentially causing problems) now that generated files
> no longer go in the source tree? Or would this cause problems for people
> importing release tarballs into other CVS trees who don't want to import
> the generated files?
>
I think we should tailor .cvsignore for use with our repository. Anyone
importing the files into another repository probably has to fix up other
things as well (killing off other files that are no-longer live, for
example), so I'm not too worried about that.
If these files are in the .cvsignore, then I think that's an error.
R.