Date: Thu, 9 Sep 1999 09:23:59 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Mike Gee <medline AT creator DOT dp DOT ua>
cc: djgpp AT delorie DOT com
Subject: Re: DJGPP wont compile C++ programs
In-Reply-To: <01befa5f$80afe200$LocalHost@mike>
Message-ID: <Pine.SUN.3.91.990909092342.6646N-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 9 Sep 1999, Mike Gee wrote:

> You know, I stumbled upon -lstdcx too; it's sure not the only problem, but
> with current DJGPP-included distribution of RHIDE (which is still 1.4) it is
> usually the first one you run into when doing quick test like 
> int main(){cout<<'Hello World';}.

First, RHIDE is not part of DJGPP, it is just one of the optional
packages.  As such, README.1ST does not cover it.  Problems specific
to RHIDE are covered in the README and other docs that come with RHIDE
itself.  And that is where users should look for the info.

And second, my experience in answering many questions from newbies
here suggests that -lstdcx is NOT the single most frequent problem.
It might seem so at times, but the long-term experience indicates
otherwise.  Documenting all those problems in a README would make it
too long.

Instead of answering these questions, README.1ST and the first chapter
of the FAQ go another way: they show how you *should* install DJGPP
and how you *should* invoke it.  If people follow those instructions,
they won't have problems.

> In fact, README does include answer on this one, but it is README from
> GCC-2.81, not from RHIDE as one would expect. FAQ does include this one too,
> but again, not in section 8.1 'GCC can't find headers or libraries'. Seems
> like a case of misplaced info, and can be frustrating for DJGPP newbies like
> me. Or maybe too general wording: explanation on -lstdcx comes under
> 'unresolved externals' section which I expected dealing with symbols like
> variables, constants etc but not with missing libraries.

You need to use the index of the FAQ.  The FAQ is such a large
document that it cannot be searched linearly or by the Table of
Contents.  That's why it is heavily indexed.  Use the indices and you
will usually find what you need in seconds, no matter how misplaced it
might seem.

> Generally DJGPP works very much out-of-the-box, and the ease of installation
> can deceive new user into not looking any farther than readme.1st in root
> dir

You don't need anything except README.1ST, unless problems pop up.
When they do, you should look in the FAQ for solutions.  If the FAQ
doesn't explain the solution, use the suggestions of section 6.15 of
the FAQ to search the DJGPP archives, and if that doesn't help,
section 6.16 tells you how to post questions here.

> A quick fix may be yet
> another <g> readme for new (clean) installation, listing in one place all
> tweaks new user should do to get rid of -lstdx errors and the kind

The FAQ *is* this document.  Most of it is about getting DJGPP to
work, and work well.  Simply use the indices, and you will see how
effective it is in answering your questions.

> PS DJGPP knowledge base would be a perfect place for such version-dependent
> fixes.

The FAQ is currently the de-facto Knowledge Base.  The next DJGPP
release adds some useful information to Knowledge Base, but it still
won't be the repository of small tricks that you seem to want.  The
FAQ should fill that gap, at least for now.

> In its current state it's next to useless for new users.

Please feel free to make it better and submit the changes.  I'm sure
they will be gladly accepted.

> Wish I have
> enough time and experience to create or maintain something like that

If you cannot do that, chances are it will never be done like you
think it should.  Nothing in DJGPP gets done without motivated
individuals that are willing to sit down and invest the efforts
necessary to make it happen.  My free time is all used up by doing
other DJGPP-related stuff, so I cannot do this myself.