Date: Sun, 08 Oct 2000 20:37:42 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: djgpp AT delorie DOT com
Message-Id: <6137-Sun08Oct2000203742+0300-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.5h
CC: matt AT gumbly DOT demon DOT co DOT uk
In-reply-to: <200010081611.LAA14031@darwin.sfbr.org> (message from jt williams
	on Sun, 8 Oct 2000 11:16:59 -0600)
Subject: Re: plptools and djgpp
References:  <200010081611 DOT LAA14031 AT darwin DOT sfbr DOT org>
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
Precedence: bulk

> From: jt williams <jeffw AT darwin DOT sfbr DOT org>
> Date: Sun,  8 Oct 2000 11:16:59 -0600
> 
> 	<http://www.gumbley.demon.co.uk/plptools.html>
> 
> If so, do they have DOS binaries they would share?
> 
> The code is (at least partially) C++, which I have no experience with. OTOH, 
> there isn't a lot of code, so could C++ be translated to C or is this not 
> usually realistic?  FWIW the configure script goes smoothly (some lfn 
> conflicts that can be fixed) until the error "no acceptable C++-compiler found 
> in $PATH."

Do you have the C++ compiler installed?  If so, you need to make sure
you set TEST_FINDS_EXE=y in the environment (the file
share/config.site, which comes with the ported Bash, does that
normally for you), and then the configure script should find gcc as
the C++ compiler.

Alternatively, set CXX=gcc in the environment, before running the
configure script.

(The above is not to say that I built plptools; it's just a general
advice how to run Unix configure scripts and live to tell the
story...)