public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bradshaw@mcs.anl.gov To: gcc-gnats@gcc.gnu.org Subject: c++/7672: can't compile c++ files Date: Tue, 20 Aug 2002 20:42:00 -0000 [thread overview] Message-ID: <200208210255.g7L2tWN00653@localhost.localdomain> (raw) >Number: 7672 >Category: c++ >Synopsis: can't compile c++ files >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Tue Aug 20 20:06:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: >Release: 3.2 >Organization: >Environment: System: Linux jedi.prototype8.net 2.4.18-5 #1 Mon Jun 10 15:31:48 EDT 2002 i686 unknown Architecture: i686 host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: i686-pc-linux-gnu configured with: ./configure --prefix=/home/rick/gcc-3.2 --with-threads=posix >Description: I write a simple hello world program with cout and include iostream and it doesn't compile and claims unknown identifier cout. #include <iostream> int main() { cout << "hello WOrld" << endl; return 0; } gccbuildtest.cpp: In function `int main()': gccbuildtest.cpp:5: `cout' undeclared (first use this function) gccbuildtest.cpp:5: (Each undeclared identifier is reported only once for each function it appears in.) gccbuildtest.cpp:5: `endl' undeclared (first use this function) >How-To-Repeat: >Fix: I am not sure how to fix but I have seen this problem ever since gcc-3.1 >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-08-21 3:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-20 20:42 bradshaw [this message] 2002-08-20 21:16 pme 2002-08-22 16:16 Gabriel Dos Reis
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=200208210255.g7L2tWN00653@localhost.localdomain \ --to=bradshaw@mcs.anl.gov \ --cc=gcc-gnats@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: linkBe 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).