From: David Enchelmaier Newsgroups: comp.os.msdos.djgpp Subject: Re: DJGPP wont compile C++ programs Date: Tue, 7 Sep 1999 09:13:56 +1000 Organization: Queensland University of Technology, Australia Lines: 36 Distribution: world Message-ID: References: NNTP-Posting-Host: sparrow.qut.edu.au Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp 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, Eli Zaretskii wrote: > > 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. > You're right... M$ has poisoned my brain, and I'm suggesting patches instead of fixing the problem properly. > 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. > Another example of the detrimental effect of M$... not caring how many pages the readme.1st takes. :) Dave ___ ___ \__ They will soar on wings like eagles __/ \_ Isaiah 40:31 _/