Date: Mon, 6 Sep 1999 09:43:52 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: David Enchelmaier <n2138166 AT sparrow DOT qut DOT edu DOT au>
cc: djgpp AT delorie DOT com
Subject: Re: DJGPP wont compile C++ programs
In-Reply-To: <Pine.OSF.4.10.9909061311580.6369-100000@sparrow.qut.edu.au>
Message-ID: <Pine.SUN.3.91.990906094333.4874M-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 6 Sep 1999, David Enchelmaier wrote:

> It seems to me that a lot of people have this problem.  I can't recall
> seeing the solution in the readme for DJGPP or RHIDE (I might be wrong,
> it's been a while and I haven't got them in front of me now), if the
> solution (or a pointer to the FAQ) isn't there, would it be worth thinking
> about adding it to the readme for the next release?

IMHO, the Right Thing is to fix problems, not to explain them in FAQs
and READMEs.  A newer version of RHIDE would probably solve this one.
The next version of DJGPP includes a [rhide] section in the DJGPP.ENV
file, which I hope will solve a large portion of these problems even
with the existing versions of RHIDE.

Anyway, a README file cannot include answers to such questions,
because it will then be so large that it will be read even less than
it is today.  -lstdcx is not the only problem that people keep bumping
into, you know.