Mail Archives: djgpp/1999/02/14/22:29:25
Tim Daniel wrote:
>
> There are now three messages on the newsgroup about the same topic on
> the RHIDE linkage environment.
[One is included here for reference]
> I have a program that compiles/links/runs fine from the command line
> when I link with libiostr.a. I have RHIDE.exe in the same directory as
> the source, and when I try to compile/link through RHIDE I get various
> errors at link time including undefined ___throw and __eh_pc. I have
> edited the DJGPP.ENV file to include libiostr in RHIDE instead of
> libstdcxx. I could not link the program with libstdcxx either from the
> command line or RHIDE without getting hundreds of errors, mainly missing
> macros. I have tried configuring RHIDE to run either with or without
> standard libraries and with and without libiostr.
>
> So my mission is to get RHIDE to use the same link environment as the
> command line and it should work. Any ideas where to start? I was
> thinking I would look for the RHIDE.env file and see whats in there.
>
> If I've missed anything in the FAQ's please point me to the right
> section and I'll happily read away.
This sounds rather as if you are mixing versions of GCC and its
libraries. With GCC 2.8.1 (which you should be using), libiostream
isn't even included. Thus, if you have one, it must come from GCC
2.7.x, and hence won't work with 2.8.x. 2.8.x is supposed to use
libstdcxx *only*.
Then, the question to be investigated is why libstdcxx doesn't work for
you. Since you already have mixed versions, it could be that your
headers are old as well, or perhaps libstdcxx itself.
If you don't have a lot of stuff done to your present DJGPP
installation, it might be simplest to nuke it and start afresh. Get all
the latest files; the Zip Picker at www.delorie.com might help here.
And if you have trouble with RHIDE searching for libstdcx.a (one x) and
not finding it, see FAQ section 8.7.
--
Nate Eldredge
nate AT cartsys DOT com
- Raw text -