This is the mail archive of the
mailing list for the GCC project.
Re: Ada files now checked in
- To: guerby at acm dot org, kenner at vlsi1 dot ultra dot nyu dot edu
- Subject: Re: Ada files now checked in
- From: mike stump <mrs at windriver dot com>
- Date: Tue, 2 Oct 2001 16:51:57 -0700 (PDT)
- Cc: gcc at gcc dot gnu dot org
> Date: Tue, 2 Oct 01 17:29:46 EDT
> From: email@example.com (Richard Kenner)
> To: firstname.lastname@example.org
> Cc: email@example.com
> I noticed these two files are generated in the original source
> directory, I believe they should be generated in the build directory
> since I assume this is standard build policy not to touch the original
> source directory (I build in a clean directory separate from the CVS
> sources as adviced by the GCC build instructions).
> I'd argue they should be in the source directory just like c-parse.c is
> in the original source directory and the reason is that the tools to build
> them may not be accessable and so these are checked in files.
This breaks (can break) multi builds when one source tree is used by
two or more build systems.
When it falls over around here, we just say, oh well, please just try
an incremental rebuild. Would be nice, if it just worked.
My other favorite, is ranlib during install:
ar ... bla.a ...
This also fails for mostly the same reason, though, this fails because
of the sharing of install tree and not the source tree. If each
operation were reasonably build/host independent and reasonably
atomic, the issue would go away.