From: Kirk <kirkrw@mediaone.net>
To: gcc-help@gcc.gnu.org
Subject: how can cout be undeclared?
Date: Fri, 08 Feb 2002 11:50:00 -0000 [thread overview]
Message-ID: <02020813570506.01192@truffula.localdomain> (raw)
I'm trying to a program ported from linux (redhat7.2 running gcc-2.96RH) to
freebsd. I have installed gcc-3.0. Most of the compile time errors that I was
getting while using gcc-2.95 on freebsd have disappeared now that I'm
compiling with gcc-30. However, there is one that is perplexing me. It is:
tveg.cpp: In member function `void TVeg::dayOut(TDay*)':
tveg.cpp:428: `cout' undeclared (first use this function)
tveg.cpp:428: (Each undeclared identifier is reported only once for each
function it appears in.)....
the whole error output is below.
It is odd that a simple cout (which compiles fine on redhat's 2.96 version)
is choking here.
Any thoughts?
Thanks in advance,
Kirk
su-2.05a$ make clean
rm *.o *~
su-2.05a$ make pnet
g++30 -c -ansi -g -Wall tday.cpp
g++30 -c -ansi -g -Wall tveg.cpp
tveg.cpp: In member function `void TVeg::dayOut(TDay*)':
tveg.cpp:428: `cout' undeclared (first use this function)
tveg.cpp:428: (Each undeclared identifier is reported only once for each
function it appears in.)
tveg.cpp: In method `void TVeg::yearOutCN(TDay*)':
tveg.cpp:464: warning: unused variable `double folC'
tveg.cpp:465: warning: unused variable `double totalN'
tveg.cpp:466: warning: unused variable `double totalM'
tveg.cpp: In method `void TVeg::understory(TDay*)':
tveg.cpp:478: warning: unused variable `double mossResp'
tveg.cpp:481: warning: unused variable `double growthResp'
*** Error code 1
next reply other threads:[~2002-02-08 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 11:50 Kirk [this message]
2002-02-08 13:41 ` Frank Geck
2002-02-08 14:14 ` Kayvan A. Sylvan
2002-02-08 16:12 ` gnu C++ compilation problem Kallol Biswas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=02020813570506.01192@truffula.localdomain \
--to=kirkrw@mediaone.net \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).