This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Status and rationale for toplevel bootstrap (was Re: Example of debugging GCC with toplevel bootstrap)

From: Paolo Bonzini <paolo dot bonzini at lu dot unisi dot ch>
To: Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>, GCC Development <gcc at gcc dot gnu dot org>
Date: Mon, 16 Jan 2006 16:06:35 +0100
Subject: Re: Status and rationale for toplevel bootstrap (was Re: Example of debugging GCC with toplevel bootstrap)
References: <10601161508.AA10274@vlsi1.ultra.nyu.edu>

Richard Kenner wrote:

   Then it seems to me that you are just relying on a peculiarity of the
   Ada build system, that is the fact that you can work entirely from
   within the GCC directory.

That's by design, of course.

Though it makes me wonder why people did not replicate the design for C++, Fortran (even old g77) and Java?

   What you need to do then, is to run from the toplevel "make
   stage3-bubble; make -C gcc gnatlib_and_tools".
Does the latter differ from "cd gcc; make gnatlib_and_tools"?

More like "(cd gcc; make gnatlib_and_tools)", i.e. the current directory is the same.

Paolo

References:
- Re: Status and rationale for toplevel bootstrap (was Re: Example of debugging GCC with toplevel bootstrap)
  - From: Richard Kenner

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]