public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "allstargrogg@wbcom.com" <allstargrogg@wbcom.com>
To: gcc-help@gcc.gnu.org
Subject: Mandrake 9.0 & GCC 3.2
Date: Thu, 10 Oct 2002 13:38:00 -0000	[thread overview]
Message-ID: <216120-2200210410203058796@wbcom.com> (raw)

I just updated to mandrake 9.0 which included a new version of GCC (3.2) as
well as a new version of the libstdc++ (5.0) and it is causing problems.  I
can't compile c++ programs that I used to be able to.  It gives me a
warning of deprecated header files and tells me to start including them as
<X> instead of <X.h>.  When I try this it then tells me I have to declare
cout and cin and endl (I was using iostream.h in this specific program)
which made absolutely no sense to me.  Also, it did not recognize the void
declaration for my main procedure.  Is this really the new standard library
being implemented, or is this just some fluke that is not correct?  Please
help.
John Grogg



             reply	other threads:[~2002-10-10 20:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-10 13:38 allstargrogg [this message]
2002-10-10 13:54 ` bjorn rohde jensen

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=216120-2200210410203058796@wbcom.com \
    --to=allstargrogg@wbcom.com \
    --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).