This is the mail archive of the
mailing list for the GCC project.
Re: cvs server: conflicts found in gcc/c-parse.c
- To: law at cygnus dot com
- Subject: Re: cvs server: conflicts found in gcc/c-parse.c
- From: Jason Merrill <jason at cygnus dot com>
- Date: 03 Mar 1998 01:13:19 -0800
- Cc: "Robert J. Brown" <rj at eli dot elilabs dot com>, Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>, egcs-bugs at cygnus dot com, "H. J. Lu" <hjl at lucon dot org>
- References: <email@example.com>
>>>>> Jeffrey A Law <firstname.lastname@example.org> writes:
> Removing the configure files is somewhat problematical since the end
> developer would have to know to go run autoconf in all the appropriate
> directories before he could configure & build. Or we have to hack
> the toplevel configure script to go run autoconf.
> And where does it put the generated configure files?
> * If they go into the local source tree, then cvs will issue
> warnings when you update your sources because your sources
> will have files not found in the repository.
So add them to .cvsignore.
> These aren't issues for things like parser generated files which
> can easily live in the object tree.
I think they should still live in the source tree, and should be included