From: "Paul G. Allen" <pgallen@randomlogic.com>
To: "Linux kernel developer's mailing list" <linux-kernel@vger.kernel.org>
Subject: Re: Which gcc version?
Date: Sat, 24 Nov 2001 04:24:57 -0800 [thread overview]
Message-ID: <3BFF9199.C01CB9FD@randomlogic.com> (raw)
In-Reply-To: <Pine.SGI.4.31L.02.0111231532000.13038141-100000@irix2.gl.umbc.edu>
John Jasen wrote:
>
> On Fri, 23 Nov 2001, J Sloan wrote:
>
> > This is all silly FUD - time for the pointer again -
> >
> > http://www.bero.org/gcc296.html
>
> Redhat apologists are given the due they deserve.
>
> Their first cut at a released 2.96 should never have made it out of the
> labs alive, and for that matter, neither should have 7.0.
>
> That said, the versions in 7.1, and the patches available have done
> reasonably well for everything that I've tried to compile (kernels
> included).
>
> What are they going to do about gcc 3.0.x? It'll be amusing to watch.
>
I installed RH 7.0 when it was released and was sorely dissappointed.
The compiler never worked for anything I tried to compile (and seeing as
how programming was 50% of my job, THAT was a MAJOR issue). I quickly
went back to RH 6.2.
That said, I now run RH 7.1 and 7.2 (depending upon the box, this one
runs 7.1 w/kernel 2.4.14).
[root@keroon /root]# gcc -v
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-85)
[root@keroon /root]#
Works just fine for everything. The problem with the RH 7.1 release is
with make, not gcc. make 3.79.x has bugs that cause, among other things,
internal assertion errors. Though it works fine for the kernel, it will
not work for many other programs (see disscussion groups, e.g. -
gnu.org, for more info). So I back-rev'd that to 3.78.1-4:
[root@keroon /root]# make -v
GNU Make version 3.78.1, by Richard Stallman and Roland McGrath.
Built for i386-redhat-linux-gnu
Copyright (C) 1988, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99
Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Report bugs to <bug-make@gnu.org>.
[root@keroon /root]#
and everything works just peachy. I compile everything for Athlon, and
it still works fine.
PGA
--
Paul G. Allen
UNIX Admin II/Network Security
Akamai Technologies, Inc.
www.akamai.com
next prev parent reply other threads:[~2001-11-24 12:25 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-23 12:53 Which gcc version? Roy Sigurd Karlsbakk
2001-11-23 12:57 ` Arjan van de Ven
2001-11-23 13:51 ` war
2001-11-23 19:43 ` J Sloan
2001-11-23 13:59 ` Anton Altaparmakov
2001-11-23 14:11 ` war
2001-11-23 15:14 ` Arjan van de Ven
2001-11-23 15:30 ` Gábor Lénárt
2001-11-23 15:34 ` Arjan van de Ven
2001-11-23 17:13 ` Re[2]: " Nerijus Baliunas
2001-11-23 19:50 ` J Sloan
2001-11-23 20:34 ` John Jasen
2001-11-23 21:55 ` J Sloan
2001-11-24 3:08 ` John Jasen
2001-11-24 12:24 ` Paul G. Allen [this message]
2001-11-26 18:31 ` Alan Cox
2001-11-27 8:42 ` Ahmed Masud
2001-11-23 16:10 ` Anton Altaparmakov
2001-11-23 14:43 ` Anton Altaparmakov
2001-11-23 16:23 ` Jeff Garzik
2001-11-23 18:30 ` Daniel Phillips
2001-11-23 18:56 ` Anton Altaparmakov
2001-11-23 19:28 ` Daniel Phillips
2001-11-23 20:14 ` Andrew Morton
2001-11-23 20:24 ` Anton Altaparmakov
2001-11-23 20:35 ` Andrew Morton
2001-11-23 21:09 ` David Weinehall
2001-11-24 16:01 ` Luigi Genoni
2001-11-24 16:09 ` Daniel Phillips
2001-11-24 17:32 ` Luigi Genoni
-- strict thread matches above, loose matches on Subject: below --
2001-11-23 17:12 RaúlNúñez de Arenas Coronado
2001-11-23 18:02 ` M. Edward (Ed) Borasky
2001-11-23 18:14 ` Thorsten Glaser
2001-04-05 10:56 which " Manoj Sontakke
2001-04-05 5:48 ` Alexander Viro
2001-04-05 14:09 ` Manoj Sontakke
2001-04-05 11:37 ` Bart Trojanowski
2001-04-05 12:02 ` Matti Aarnio
2001-04-05 12:26 ` David Woodhouse
2001-04-05 12:31 ` Matti Aarnio
2001-04-05 13:09 ` Richard B. Johnson
2001-04-05 11:45 ` Matti Aarnio
2001-04-05 11:50 ` christophe barbe
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=3BFF9199.C01CB9FD@randomlogic.com \
--to=pgallen@randomlogic.com \
--cc=linux-kernel@vger.kernel.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