Date:	Thu, 1 Feb 1996 08:51:30 -0500
From:	dj (DJ Delorie)
To:	oandico AT eee DOT upd DOT edu DOT ph
CC:	djgpp AT delorie DOT com
In-reply-to:	<Pine.SOL.3.91.960201195803.233A-100000@gollum> (message from Orlando Andico on Thu, 1 Feb 1996 20:03:02 -0800 (GMT))

> Surprisingly, this step produced a set of executables, but the instructions
> say something about recompiling GCC with itself or something... a pretty 
> long step. It seems like this is just about checking the compiler. Can I 
> skip this step? after all, I already have a set of executables.

The idea is that gcc doesn't trust the syste compiler, so you build
the first version with no optimization (safer), then use that gcc to
build a new version with full optimization.  Since djgpp *is* gcc, you
don't need the second step.

To do the second step, just make a "stage1" directory, move gcc.exe
(renamed from xgcc.exe), cc1.exe, and cpp.exe (renamed from cccp.exe)
to the stage1 directory, do "rm *.o xgcc cc1 cccp" and then follow the
stage 2 instructions.

> Is it safe to use my old header files, or does each new version of GCC 
> come with a new set of headers? after the make finishes its mess, I have 
> the executables in a path off the main source tree. Can I transfer these 
> directly to my DJGPP bin directory?

djgpp V2 provides its own headers; you do not use the ones from gcc.

- Raw text -