From: Felix Natter <f DOT natter AT ndh DOT net>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Help a newbie today: where is -lstdcx?
Date: 09 Oct 1999 15:04:15 +0200
Organization: Customer of NDH Netzwerkdienste Hoeger GmbH
Message-ID: <wkzoxs65yo.fsf@mail.ndh.net>
References: <38010890 DOT 2163932 AT news DOT telepac DOT pt>
NNTP-Posting-Host: port253.bonn.ndh.net
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: passat.ndh.net 939473951 982 195.94.93.253 (9 Oct 1999 12:59:11 GMT)
X-Complaints-To: abuse AT ndh DOT net
NNTP-Posting-Date: 9 Oct 1999 12:59:11 GMT
User-Agent: Gnus/5.070084 (Pterodactyl Gnus v0.84) Emacs/20.4
Lines: 36
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com


I AT hate DOT spam DOT so DOT much DOT it DOT hurts DOT com (Noway José) writes:
> I used this setup to make allegro, and it worked perfectly.
> When I try to compile a simple C++ program, rhide's message window
> reportes that ld.exe "cannot open -lstdcx: no such file or directory
> (ENOENT)". What am I doing wrong?
> Thanks in advance.

hi,

this is a very old problem, that stems back to when gcc-2.7.x was
the latest gcc. since then, there has been a change in what the
LFN-Variable (long-filenames)
means. And because Rhide still thinks of this variable
in the way that it was used with gcc 2.7.x, it misinterprets it,
and usually disables "LFN", and libstdcxx.a needs LFN (9.3),
that's why it gives you an error.
this explanation is taken from:
http://www.delorie.com/howto/rhide/lstdcx-fix.html
in this document, it is also explained how you can fix it:
add
[RHIDE]
RHIDE_TYPED_LIBS. =stdcxx
to your djgpp.env-file (be careful with trailing whitespace)
or get a new release of rhide (why hasn't there been a new release
for so long ?)

btw, you've downloaded lgpp*, these are c++ class libraries,
which most people don't need, and they are not maintained anymore.

good luck,
--
Felix