From: Nate Eldredge <neldredge AT hmc DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: iostream problems
Date: 12 Nov 1999 15:44:24 -0800
Organization: InterWorld Communications
Lines: 35
Message-ID: <83g0ybff6v.fsf@mercury.st.hmc.edu>
References: <iU0X3.2448$K5 DOT 472344 AT typhoon2 DOT gnilink DOT net>
NNTP-Posting-Host: mercury.st.hmc.edu
X-Trace: nntp1.interworld.net 942450321 1432 134.173.45.219 (12 Nov 1999 23:45:21 GMT)
X-Complaints-To: usenet AT nntp1 DOT interworld DOT net
NNTP-Posting-Date: 12 Nov 1999 23:45:21 GMT
X-Newsreader: Gnus v5.7/Emacs 20.4
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

"Drake Wilson" <drake AT libcom DOT com> writes:

> I am a C++ student.  The only C++ compilers I have are Turbo C++, very old
> and clunky, and Visual C++, which creates a bunch of files unnecessary for
> what I'm doing (i.e. workspace, project, debug folder, etc.) -- and when I
> go to look at my directory structure, maybe one Debug folder wrote over
> another or something, good grief -- which is why I downloaded DJGPP.
> However, I need to use the iosteam -- excuse me, iostream.h classes, which
> somehow don't work in DJGPP.  I am running Windows 95 (DOS 7), and RHIDE is
> complaining about not being able to find streambuf.h.  I tried searching
> through my DJGPP directory, and the file does not exist.  Can any DJGPPers
> help me with my dilemma?

First, did you download the lgp*b.zip package (to match your version
of gpp*b.zip)?  That's where the file is.

If you did download and install that package, your problem is most
likely to do with long file names.  The full explanation is long, but:

* If you intend to use DJGPP from "command prompt only mode", you
  won't be able to access long file names; you'll see short aliases
  (micros~1.txt) instead.  In this case, you should unpack the DJGPP
  packages with an unzipper that does not know about long file names.
  PKUNZIP is a good one.

* If you intend to use DJGPP from a Windows DOS box, you will be able
  to see long file names.  You should unpack with Winzip or something
  else that does understand long file names.

FAQ section 8.2 talks about this.

-- 

Nate Eldredge
neldredge AT hmc DOT edu