Mail Archives: djgpp/1999/09/08/23:53:32
Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote in article
<Pine DOT SUN DOT 3 DOT 91 DOT 990906094333 DOT 4874M-100000 AT is>...
> 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.
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';}.
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. I finished
searching \djgpp tree for '-lstdcx' - not a best way to find something. (Now
that I think of it, it was the fastest solution, only a few minutes wasted,
compared to half-hour I spend trying to find solution in less bruteforce way
:)
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, while it still needs (at least for me) some slight tweaking, documented,
but unfortunately scattered through several readme files. I understand the
reasons for it, but its a problem nevertheless. 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, something
of a HOWTO like Johan Venter does on RSXNTDJ. Almost all information that
user need is already here, the problem is sometimes it's fragmented and hard
to find.
PS DJGPP knowledge base would be a perfect place for such version-dependent
fixes. In its current state it's next to useless for new users. Wish I have
enough time and experience to create or maintain something like that -
reasonably organized and up-to-date reference as a programmer's tool beats
anything. I'm still keeping old quickhelp files from MSC 6.0 - haven't seen
better programming reference since. It included just about everything from
syntax to opcodes.
Well, my 2c anyway.
- Raw text -