From: Oscar Fuentes <ofv@wanadoo.es>
To: Pete Barrie <peter@cis.strath.ac.uk>
Cc: gcc-help@gcc.gnu.org
Subject: Re: cygwin gcc 3.0.4 problem
Date: Sun, 10 Mar 2002 12:58:00 -0000 [thread overview]
Message-ID: <wuwkt9z1.fsf@wanadoo.es> (raw)
In-Reply-To: <5.1.0.14.0.20020310200531.021ebcd0@pophost.cs.strath.ac.uk>
Pete Barrie <peter@cis.strath.ac.uk> writes:
> Win2000 Cygwin 1.3.10-1 binutils 2.11.2
>
> Hi. I've just built 3.0.4 native on Cygwin. Build seemed to
> go fine and I can compile/run C prog hello.c
>
> However C++ hello.cpp fails as shown below. Is this something
> trivial I am missing?
>
> Thanks for any help
>
> Pete
>
> $ cat hello.cpp
> #include <iostream.h>
>
> int main ()
> {
> cout << "Hello World!";
> return 0;
> }
>
>
>
> $ gcc -v hello.cpp
Does it fail with
$ g++ hello.cpp
???
g++ automatically links the libraries needed by the C++ library. GCC
not.
BTW,
#include <iostream.h>
is not standard C++. Use
#include <iostream>
--
Oscar
next prev parent reply other threads:[~2002-03-10 20:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-10 12:29 Pete Barrie
2002-03-10 12:58 ` Oscar Fuentes [this message]
2002-03-10 13:03 ` Oscar Fuentes
2002-03-10 13:02 ` Kayvan A. Sylvan
2002-03-10 14:08 ` Pete Barrie
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=wuwkt9z1.fsf@wanadoo.es \
--to=ofv@wanadoo.es \
--cc=gcc-help@gcc.gnu.org \
--cc=peter@cis.strath.ac.uk \
/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).