Date:	Tue, 24 Mar 1998 13:13:40 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Bob Paddock <bpaddock AT csonline DOT net>
cc:	djgpp AT delorie DOT com, Robert Hoehne <robert DOT hoehne AT gmx DOT net>
Subject:	Re: Can't Get GCC 2.8.0 to build?
In-Reply-To:	<4fkF1UQy8cQE092yn@csonline.net>
Message-ID:	<Pine.SUN.3.91.980324131259.21946G-100000@is>
MIME-Version:	1.0

On Mon, 23 Mar 1998, Bob Paddock wrote:

> # Common prefix for installation directories.
> # NOTE: This directory must exist when you start installation.
> prefix = \$$DJDIR

This *is* the cause of the problem.

> I'll change it to point at \DJGPP, or should that be %DJDIR%?

Neither.  Change it to ${DJDIR}, and it should work.

Robert, I think you should use ${DJDIR} instead of $$DJDIR as the
argument to configure script, and then it should work without any
trouble.

> I still think I'm missing some thing as I don't see any
> thing that fixes the files names to end with .exe in the
> "install" section of the makefile nor any other scripts that
> would fix them.

This one, I don't understand.  Doesn't the Makefile cause GCC to be
invoked like this (for example, for cc1):

	gcc -o cc1 ....

If the above is true, DJGPP's port of GCC is set to generate *both*
cc1 and cc1.exe.  The former makes Make happy (since the target of the
rule gets created), while the latter makes DOS (and you) happy.

The only way I can explain this failure is that the GCC build
procedure overrides the specs file with a different copy, possibly one
which comes with the GCC distribution.  The magic which causes both
cc1 and cc1.exe be generated is implemented in the %DJDIR%/lib/specs
file, and if an incompatible specs file is used, it could disable this
feature.

Robert, can you help explain this phenomenon?

- Raw text -