This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: fixinc
- To: rittle at rsch dot comm dot mot dot com
- Subject: Re: PATCH: fixinc
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 29 Nov 2000 00:58:18 -0200
- Cc: gcc-patches at gcc dot gnu dot org
- Organization: GCC Team, Red Hat
- References: <200011290245.UAA56150@latour.rsch.comm.mot.com>
On Nov 29, 2000, Loren James Rittle <rittle@latour.rsch.comm.mot.com> wrote:
> However, I just started building from that source tree on another
> machine that may only mount it read-only.
> I have no idea if the powers that be want this patch since I suppose
> that it has the possibility of masking a real error...
Yep. And there are many other situations in which you'd need write
access to the build tree. For all bison-generated files, for
example.
What i generally do is to run an initial build (not necessarily
bootstrap) on a machine that has write access to my tree, then start
building on other machines that have read-only access.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me