From: aadhanda AT bellatlantic DOT net
Newsgroups: comp.os.msdos.djgpp
Subject: Iostream.h error
Date: Thu, 16 Apr 1998 15:51:48 -0400
Organization: Bell Atlantic Internet Solutions
Lines: 44
Message-ID: <35366154.F619434E@bellatlantic.net>
NNTP-Posting-Host: client-118-143.bellatlantic.net
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="------------97330E9B04A0EE5F5FF15391"
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk
--------------97330E9B04A0EE5F5FF15391
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hello,
I was wondering if someone could help me. I am learning C++ and
when i try to run the file
hello.cpp under DJGPP using "gcc -c -Wall hello.cpp" it says:
hello.cpp:1 iostream.h: no such file or directory (EOENT)
In the faq it mentions this problem and says to download the file
lgp271b.zip. I do not have this file
but use the lgpp280b selected from the "zip picker" on the DJGPP
homepage. I do not know if one
is an updated version of the other or if they are two different files,
if somebody could help me it
would be appreciated, thanks.
--------------97330E9B04A0EE5F5FF15391
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hello,
I was wondering if someone could help me.
I am learning C++ and when i try to run the file
hello.cpp under DJGPP using "gcc -c -Wall hello.cpp" it says:
hello.cpp:1 iostream.h: no such file or directory (EOENT)
In the faq it mentions this problem and says to download the file lgp271b.zip.
I do not have this file
but use the lgpp280b selected from the "zip picker" on the DJGPP
homepage. I do not know if one
is an updated version of the other or if they are two different files,
if somebody could help me it
would be appreciated, thanks.
--------------97330E9B04A0EE5F5FF15391--
a project I'm working on is completely stalled until I have a
cc1plus.exe that will faithfully
> compile my code under the sole condition that the code be syntactically
correct.
Assuming you are developing the code still may I suggest using the following
CFLAGS ..
gcc -Wall -W -Werror -gstabs -O2
Once it is mostly developed then bump up the -O level.
>#include
Note that I am no c++ expert, but I believe that when you #include
here you are actually including a ton of source code. Unlike regular c
header files where you just get prototypes I think you actually get code
here. PGCC needs to store entire functions in memory at a time, so if the
class (or anything else included from it) is big that can jack up memory
usage.
Yeah, pgcc is a memory cow. Try emailing the beast list and perhaps someone
can tell you which optimizations in particular are memory intensive without
much of a performance gain.
Andy