From:	jack <jacko11 AT telegram DOT infi DOT net>
Newsgroups:	comp.os.msdos.djgpp
Subject:	C++ Compile Problem with DJGPP 2.8.1
Date:	Tue, 09 Jun 1998 01:59:10 -0400
Organization:	InfiNet
Lines:	32
Message-ID:	<357CCF2D.70992FFA@telegram.infi.net>
Reply-To:	nospamme AT delorie DOT com
NNTP-Posting-Host:	pa4dsp2.orh.infi.net
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Hi!

I recently got DJGPP; I tested the C compiler and the C libs, using both
RHIDE 1.4 and the command line tools, checking both out. I'm running
under DOS62 with no long filenames.

I saw in one of the files that I should add a "rhide.env" file
containing the string:

RHIDE_TYPED_LIBS_DJGPP.cc=stdcxx

since RHIDE would ordinarily be looking for stdcx and it had changed. So
I did this before trying C++. I did a "hello,world" program with
printf() and it worked great. Then I did a C++ (.cc) hello, world
program, still using stdio. It worked.

Then I did a C++ "Hello" with iostreams, and it started compiling. But
it never stops clicking the disk light... it just keeps going and going
and going. I tried this in both RHIDE and plain GCC command line. 

I didn't realize that the "lib" would be attached to stdcxx, making it
one character too long for the 8.3 scheme of DOS. And since I am using
truncated filenames, RHIDE might be looking for it in the wrong place
and maybe just keeps looking? I don't know; I should change it back
since it would be truncated to the old filename.

But if the new filename is too long for dos, (libstdcxx.a) then perhaps
this is why it doesn't work with GCC.EXE either.

Does anyone know how to solve this?

BTW Love the compiler (at least the part that works so far :-))

- Raw text -