Date: Wed, 10 Sep 1997 20:07:42 -0700 (PDT)
Message-Id: <199709110307.UAA07673@adit.ap.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
From: Nate Eldredge <eldredge AT ap DOT net>
Subject: Re: Rebuilding gcc -- cc1plus and gxx not made
Cc: djgpp AT delorie DOT com
Precedence: bulk

At 11:56  9/10/1997 +0300, you wrote:
>
>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.
Well... without using bash it doesn't work, the makefile bombs out on the
line `genattr config/i386/i386.md > t-attr.h'. With bash (and changing the
Makefile `SHELL=' to bash), it works fine. Also, I think one of the
makefiles contains a line with backquotes, implying that it needs bash. At
any rate, having bash seems to greatly simplify things, and it's probably
easier to get it than to research and fix the things that don't work
otherwise. So I think using only `stock DOS tools' is only important to a
purist.
>
>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.
I mentioned that the solution is to run `make' in the `cp' subdirectory.
>
>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.
Cool.

Nate Eldredge
eldredge AT ap DOT net