mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anton Altaparmakov <aia21@cam.ac.uk>
To: 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 16:10:48 +0000	[thread overview]
Message-ID: <5.1.0.14.2.20011123160559.00a8d8b0@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <20011123163019.A5418@vega.digitel2002.hu>
In-Reply-To: <3BFE67E8.CFA0D371@redhat.com> <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>

At 15:30 23/11/01, =?iso-8859-2?B?R+Fib3IgTOlu4XJ0?= wrote:
>On Fri, Nov 23, 2001 at 03:14:48PM +0000, Arjan van de Ven wrote:
> > war wrote:
> > >
> > > #1) The compiler from redhat (gcc-2.96) is not an official GNU release.
> > > #2) http://www.atnf.csiro.au/~rgooch/linux/docs/kernel-newsflash.html/
> > >       "the reccomend compiler is now gcc-2.95.3, rather than gcc-2.91.66"
> >
> > From Documentation/Changes in 2.4.15:
> >
> > The Red Hat gcc 2.96 compiler subtree can also be used to build this
> > tree.
> > You should ensure you use gcc-2.96-74 or later. gcc-2.96-54 will not
> > build
> > the kernel correctly.
>
>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. It was very ROTFL RedHat to release kgcc to be
>able to compile kernel. And these type of distributions are marked as even
>enterprise-ready and likes by RedHat :) Sorry for the flame, but IMHO it's
>very funny :) [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 ...]

Oh, I have to look at your configure.in for how you do that so I can add 
the opposite check to linux-ntfs and refuse to compile if gcc-2.96 or 3.x 
is NOT used. (-:

>But for being more serious: do newer gcc 2.96 versions have these type of
>errors? I mean mainly incompatible object format ...

I don't know about that. All I can say is that since RedHat 7.0 and the 
updated gcc-2.96 (the first release was indeed broken) I have been using 
gcc-2.96 for everything and I haven't experienced any problems with it 
(compiling both kernels and user space code with it but YMMV as I don't 
compile that much user space code myself except for my own code which 
obviously works considering I write it for gcc-2.96...). I even installed 
gcc-2.96 on my SuSE 7.2 system and that has been happy with it, too.

Anton


-- 
   "I've not lost my mind. It's backed up on tape somewhere." - Unknown
-- 
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Linux NTFS Maintainer / WWW: http://linux-ntfs.sf.net/
ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/


  parent reply	other threads:[~2001-11-23 16:12 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-23 12:53 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
2001-11-26 18:31             ` Alan Cox
2001-11-27  8:42               ` Ahmed Masud
2001-11-23 16:10     ` Anton Altaparmakov [this message]
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=5.1.0.14.2.20011123160559.00a8d8b0@pop.cus.cam.ac.uk \
    --to=aia21@cam.ac.uk \
    --cc=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

all inboxes | Powered by JetHome®