Date: Wed, 10 Sep 1997 11:56:29 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Nate Eldredge <eldredge AT ap DOT net>
cc: "Peter J. Farley III" <pjfarley AT dorsai DOT org>, djgpp AT delorie DOT com
Subject: Re: Rebuilding gcc -- cc1plus and gxx not made
In-Reply-To: <199709100234.TAA28521@adit.ap.net>
Message-ID: <Pine.SUN.3.91.970910115557.9494G-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Tue, 9 Sep 1997, Nate Eldredge wrote:

> I don't think there's any official documentation, however, here are the
> steps I followed to get gcc to build successfully. It was rather confusing.
> You need to have bash; I don't think you can build without it.

I don't think this is correct.  AFAIK, all the times DJ built gcc in
the past, he didn't use Bash at all.  He did it with stock DOS tools
and a few auxiliary programs like rm, mv etc.

I'd guess that the C++ compiler won't build automatically because DJ
never does it that way.  He always builds C and C++ separately,
because in DJGPP, they are in different distributions (the C compiler
in gccNNNb.zip, the C++ compiler in gppNNNb.zip).

So the solution would be to invoke that mk.bat or whatever manually.

This all will probably change with the next release, since GCC has
switched to autoconf, and I guess Bash *will* be used from now on.