Mail Archives: djgpp/1998/04/12/21:30:40
From: | "John M. Aldrich" <fighteer AT cs DOT com>
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Re: Help with Rhide linking
|
Date: | Sun, 12 Apr 1998 20:16:42 -0400
|
Organization: | Two pounds of chaos and a pinch of salt.
|
Lines: | 38
|
Message-ID: | <3531596A.7B4C@cs.com>
|
References: | <01bd660e$4e4baec0$ec40a8c2 AT j DOT couston>
|
NNTP-Posting-Host: | ppp244.cs.com
|
Mime-Version: | 1.0
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Jamie wrote:
>
> After having just lost my trusty old Borland C++ compiler (version 3 I
> think) due to Hard Drive failure, I was extremely pleased to note the
> similarities between it and Rhide. I downloaded and decompressed all of the
> files as instructed to and all seemed fine.
>
> There is one problem though. I can compile and link C programs fine but the
> linker issues an error whenever a C++ source is linked. The source compiles
> fine but then I get the following error,
>
> Error: c:/djgpp/bin/ld.exe: cannot open -lstcdx: No such file or directory
> (ENOENT)
>
> Can anyone please help, Its driving me insane!
<cut and pasted from one of about 10 identical replies to this question
in the last week; if this keeps up Eli will need to write a new FAQ
chapter...>
RHIDE 1.4 wasn't designed with gcc 2.8.0 in mind. The solution is
simple: edit the file %DJDIR%/share/rhide/rhide.env (or create it if it
doesn't already exist), and put the following line in it:
RHIDE_TYPED_LIBS_DJGPP.cc=stdcxx
After doing this, RHIDE should link C++ programs correctly.
Good luck!
--
---------------------------------------------------------------------
| John M. Aldrich | "Always listen to experts. They'll |
| aka Fighteer I | tell you what can't be done, and why.|
| mailto:fighteer AT cs DOT com | Then do it." |
| http://www.cs.com/fighteer/| - Lazarus Long |
---------------------------------------------------------------------
- Raw text -