From: Arjan van de Ven <arjanv@redhat.com>
To: "Gábor Lénárt" <lgb@lgb.hu>
Cc: Arjan van de Ven <arjanv@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Which gcc version?
Date: Fri, 23 Nov 2001 10:34:34 -0500 [thread overview]
Message-ID: <20011123103434.A24669@devserv.devel.redhat.com> (raw)
In-Reply-To: <20011123125137Z282133-17408+17815@vger.kernel.org> <5.1.0.14.2.20011123135801.00aad970@pop.cus.cam.ac.uk> <3BFE591B.D1F75CD5@starband.net> <3BFE67E8.CFA0D371@redhat.com> <20011123163019.A5418@vega.digitel2002.hu>
In-Reply-To: <20011123163019.A5418@vega.digitel2002.hu>; from lgb@lgb.hu on Fri, Nov 23, 2001 at 04:30:19PM +0100
On Fri, Nov 23, 2001 at 04:30:19PM +0100, Gábor Lénárt wrote:
> True, but as it's known, gcc-2.96 is NOT an official gcc release by the gcc
> team. It was RedHat's fault to fetch a development CVS gcc snapshot and
> release it as gcc 2.96 in RedHat distributions, while object format used by
> 2.96 is not compatible with 2.95 nor 3.0.x at least according information
> can be found on site of gcc.
That is only the case for C++. And the same is true for egcs -> 2.95.x and
from 2.95.x -> 3.0.x and from 3.0.x -> 3.1
> It was very ROTFL RedHat to release kgcc to be
> able to compile kernel.
gcc 3.0 doesn't compile 2.2 kernels. "2.96" is like 3.0 in that respect. All
2.4 kernel RPMs from Red Hat are compiled with the "2.96" gcc.
> [Also, while developing MPlayer we had got problems with even
> newer 2.96's, so we do not recommend it in the dox, and ./configure won't
> able you to use 2.96 without a special configure switch ...]
I noticed yes. Most likely a case of broken inline asm.....
gcc 3 will break just as much
next prev parent reply other threads:[~2001-11-23 15:34 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 [this message]
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
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=20011123103434.A24669@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=lgb@lgb.hu \
--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