From:	"Andrew Crabtree" <andrewc AT rosemail DOT rose DOT hp DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: PGCC and rhide
Date:	Tue, 3 Mar 1998 16:20:36 -0800
Organization:	Hewlett Packard
Lines:	27
Message-ID:	<6di6oe$8dk$1@rosenews.rose.hp.com>
References:	<Pine DOT GSO DOT 3 DOT 96 DOT 980224111554 DOT 13318F-100000 AT almos DOT vein DOT hu> <3 DOT 0 DOT 5 DOT 32 DOT 19980303224955 DOT 007b5950 AT math DOT amu DOT edu DOT pl>
NNTP-Posting-Host:	ros51675cra.rose.hp.com
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Maciej Radziejewski wrote in message
<3 DOT 0 DOT 5 DOT 32 DOT 19980303224955 DOT 007b5950 AT math DOT amu DOT edu DOT pl>...
>>RHIDE_GCC=pgcc
>I just wanted to note, that adding these two lines prevents
>my installation of RHIDE from performing the compilation.
>I get the 'Bad command or file name' message in the compile
>window.
Note that I don't have rhide, and I also don't have a dual gcc installation
so this is a guess.

Presumably, rhide is trying to execute a program named pgcc.exe.  It won't
find it because by default
the zip file overwrites your existing gcc.exe.  If you were really clever,
you could keep your old gcc.exe, and have the new gcc.exe by pgcc.exe.  Then
you could install the corresponding new pre-processor and compiler (cpp.exe
and cc1.exe) into a special directory (like djgpp/bin/pgcc or something),
last you would modify djgpp.env and create a special entry for pgcc.exe and
have its search path look in your new directory before looking in regular
bin directory.  This way, you could just say 'gcc foo.c' or 'pgcc foo.c' and
have both compilers installed at the same time.

This might actually be a really smart way to go, although it does eat up a
little more disk space.  Robert is changing around gcc 2.8 to be more unix
like (having target/version subdirs), so I may switch over once that is
finalized.  But the current way is clean and easy assuming pgcc works :)

- Raw text -