Date:	Sun, 25 Jun 2000 10:34:49 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Jim Meier <fatjim AT home DOT com>
cc:	djgpp AT delorie DOT com
Subject:	Re: "installation problem, cannot exec `cpp'"
In-Reply-To:	<dnc55.35210$aO5.218806@news1.sshe1.sk.home.com>
Message-ID:	<Pine.SUN.3.91.1000625103423.25761K-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sun, 25 Jun 2000, Jim Meier wrote:

> > I think the FAQ (section 6.5) is pretty explicit, and tells you
> > exactly what to do: find cpp.exe and make sure that it is in the
> > directory where GCC looks for it.  What exactly is not clear in the
> > FAQ?
> 
> The fact that cpp IS in my path :)

Perhaps you have an old version of the FAQ.  The latest one (available
as v2/faq230b.zip from the DJGPP ftp sites) explains that the newer
versions of GCC don't put cpp.exe on the PATH, they put it in a
subdirectory of the lib/gcc-lib directory, e.g. lib/gcc-lib/2.952.

If you have cpp.exe on your PATH, I suspect you have a mix of
different GCC versions installed.  Try "cpp -v" and "gcc --version"
and see what versions do they print.  (In the case of cpp, you will
have to type ^Z to get back to the command line.)  If they print
different versions, you will have to uninstall GCC and install it
again from scratch.

> There was mention in the FAQ about an envvar "COMPILER_PATH" - my djgpp.env
> doesn't have one.

This is normal: latest versions of DJGPP don't have (and don't need)
COMPILER_PATH.

- Raw text -