mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anton Altaparmakov <aia21@cam.ac.uk>
To: war <war@starband.net>
Cc: Roy Sigurd Karlsbakk <roy@karlsbakk.net>, linux-kernel@vger.kernel.org
Subject: Re: Which gcc version?
Date: Fri, 23 Nov 2001 13:59:48 +0000	[thread overview]
Message-ID: <5.1.0.14.2.20011123135801.00aad970@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <3BFE5447.3AFDFFD3@starband.net>
In-Reply-To: <20011123125137Z282133-17408+17815@vger.kernel.org>

At 13:51 23/11/01, war wrote:
>You should use gcc-2.95.3.

That's not true. gcc-2.96 as provided with RedHat 7.2 is perfectly fine.

gcc-3x OTOH is not a good idea at the moment.

Anton


>Roy Sigurd Karlsbakk wrote:
>
> > hi all
> >
> > I just wonder...
> > With a clean rh72 install, I've got two gcc versions installed in parllel,
> > 2.96 and 3.0.2. Which one should I use to compile the kernel?
> >
> > thanks
> >
> > roy
> > --
> > Roy Sigurd Karlsbakk, MCSE, MCNE, CLS, LCA
> >
> > Computers are like air conditioners.
> > They stop working when you open Windows.
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/

-- 
   "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 14:01 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 [this message]
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
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.20011123135801.00aad970@pop.cus.cam.ac.uk \
    --to=aia21@cam.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roy@karlsbakk.net \
    --cc=war@starband.net \
    /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®