From: Paolo Carlini <pcarlini@unitus.it>
To: mikema@cc.gatech.edu
Cc: gcc-help@gcc.gnu.org
Subject: RE: the problem about difference between gcc2.7 and gcc2.96
Date: Mon, 15 Oct 2001 12:03:00 -0000 [thread overview]
Message-ID: <3BC9807D.1AD10846@unitus.it> (raw)
Hi,
a few sparse considerations (not about the specific problem you mention):
1- Despite its misleading name, gcc2.96 is *not* an official GNU release (see,
f.i., http://gcc.gnu.org/ml/gcc-announce/2000/msg00003.html ) and you should more
appropriately contact the RedHat support.
2- If you want to stick with RedHat development tools, you may consider trying
gcc2.96-99 (vs 2.96-81, right?) which is part of the "unstable" Rawhide
distribution (f.i., ftp://ftp.redhat.com/pub/redhat/linux/rawhide/ ) and in
general is less buggy.
3- If you are still in the process of updating your development chain (from the
very old 2.7.x) consider testing GNU's gcc2.95.3 or the new 3.0.x series of
official releases (3.0.x is also available as *rpm packages in the Rawhide
distribution, by the way).
Regards,
Paolo Carlini.
next reply other threads:[~2001-10-15 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-15 12:03 Paolo Carlini [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-13 18:27 ma, yi
2001-12-02 8:27 ` Alexandre Oliva
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=3BC9807D.1AD10846@unitus.it \
--to=pcarlini@unitus.it \
--cc=gcc-help@gcc.gnu.org \
--cc=mikema@cc.gatech.edu \
/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).