Date: Sun, 14 Nov 1999 13:04:19 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Laurynas Biveinis <lauras AT softhome DOT net>
cc: DJGPP Workers <djgpp-workers AT delorie DOT com>
Subject: Re: GCC porting questions
In-Reply-To: <382E8342.86EE7678@softhome.net>
Message-ID: <Pine.SUN.3.91.991114130124.19268B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 14 Nov 1999, Laurynas Biveinis wrote:

> 1) Stage 1 - System compiler compiles GCC's C compiler only
> 2) Stage 2 - That C compiler from stage 1 compiles itself again, also it
> compiles C++, Fortran etc. compilers.
> 3) Stage 3 - C compiler from stage 2 compiles itself and C++, Fortran etc. one 
> more time.
> 4) Stage 2 and stage 3 compilers are compared - if they differ, it indicates a
> bug in gcc.

You describe the bootstrap, all right.  However, if a previous version 
of GCC is already installed, you don't need all those steps.  You can 
simply do stage 1 and 2, or even directly stage 2.

That's how all versions of GCC up to (and including) 2.8.x were
compiled for DJGPP.  I do the same on Unix if some version of GCC
is already available.