From: bukinm AT inp DOT nsk DOT su (Michael Bukin)
Newsgroups: comp.os.msdos.djgpp
Subject: pgcc and GCC_EXEC_PREFIX
Date: Thu, 12 Jun 1997 16:00:02 GMT
Organization: BINP SD RAS
Lines: 22
Message-ID: <33a11341.3847658@news-win.inp.nsk.su>
Reply-To: bukinm AT inp DOT nsk DOT su
NNTP-Posting-Host: csd-bsdi.inp.nsk.su
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

There was a problem with pgcc snapshots don't understand
GCC_EXEC_PREFIX. I mean, when it was set like this:
-- part of djgpp.env ---
[pgcc]
GCC_EXEC_PREFIX=%DJDIR%/bin/p
--
then, according to documentation for gcc, calling pgcc should
try djgpp_dir/bin/pcpp for cpp pass, then in standard place,
and then in PATH. But it always called cpp instead of pcpp.

It turns out, that pgcc searches for compilation stages without
appending .exe extensions (original gcc from DJGPP can handle
GCC_EXEC_PREFIX).

Having pcpp without .exe extension solves the problem.
(Workaround was to use pgcc symlinked to gcc from original
DJGPP distribution).

Not that I need it that much now, but is it possible
to make pgcc behave in the way original gcc does.
Just it looks ugly without extension :)