From: Ryan O'NEil <talisman580@yahoo.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] which linux! which gcc!
Date: Fri, 8 Jun 2001 08:38:51 +0000 [thread overview]
Message-ID: <fd3bf02f.0106071312.1231c5ee@posting.google.com> (raw)
In-Reply-To: <200106021653.SAA25202@rackham.cd.chalmers.se>
Yes RedHat made the unfortunate choice of releasing gcc 2.96,
which the gcc group explicitly stated was not meant for release.
Same goes for Mandrake and who knows what others. *sigh*
lac@cd.chalmers.se (Laura Creighton) wrote in message news:<200106021653.SAA25202@rackham.cd.chalmers.se>...
> If you are running Red Hat 7.0 then stop what you are doing
> immediately. the gcc is entirely hosed. there are so many
> bugs you cannot compile anything with it.
next prev parent reply other threads:[~2001-06-08 8:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-02 16:53 Laura Creighton
2001-06-02 18:02 ` andrey mirtchovski
2001-06-02 17:45 ` Jim Choate
2001-06-03 7:20 ` Boyd Roberts
2001-06-04 11:55 ` Theo Honohan
2001-06-03 6:54 ` Boyd Roberts
2001-06-08 8:38 ` Ryan O'NEil [this message]
2001-06-02 17:41 anothy
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=fd3bf02f.0106071312.1231c5ee@posting.google.com \
--to=talisman580@yahoo.com \
--cc=9fans@cse.psu.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 NNTP newsgroup(s).