From: 520075708323-0001@t-online.de (Alexander Helm)
To: Geoffrey <esoteric@3times25.net>
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc 3.2
Date: Sun, 22 Dec 2002 18:18:00 -0000 [thread overview]
Message-ID: <3E06056F.9050709@fs.tum.de> (raw)
In-Reply-To: <3E05E8B1.6040705@3times25.net>
Hi Geoffrey,
mostly it's the code (missing "std::cout" or "using namespace std;").
Furthermore 3.2 is more standard compliant thus resulting in error
messages not thrown whilest using 2.9x.
AFAIK there are some small FAQs around and at least some information on
gcc.gnu.org
CU
Alexander
Geoffrey wrote:
> Recent upgrade to Mandrake 9.0 brought with it gcc 3.2. Now I'm finding
> all kinds of software that compiled fine with 2.9? will not compile with
> 3.2. memtest86 and speechtools 1.2.2 for festival are two examples.
>
> Anyone else having such problems? Is it the code or the compiler?
>
next prev parent reply other threads:[~2002-12-22 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-22 8:27 g++ man pages umapathy
2002-12-22 10:33 ` umapathy
2002-12-22 13:58 ` gcc 3.2 Geoffrey
2002-12-22 18:18 ` Alexander Helm [this message]
2002-12-23 1:32 ` g++ man pages LLeweLLyn Reese
2008-02-22 13:28 gcc 3.2 shakeeb ahmed
2008-02-22 16:04 ` Eljay Love-Jensen
2008-02-24 2:23 ` Manuel López-Ibáñez
2008-02-24 7:09 ` Mihai Donțu
2008-02-24 10:06 ` Eljay Love-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=3E06056F.9050709@fs.tum.de \
--to=520075708323-0001@t-online.de \
--cc=esoteric@3times25.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).