From: Wakko Warner <wakko@animx.eu.org>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Ro0tSiEgE <ro0tsiege@bjstuff.com>, linux-kernel@vger.kernel.org
Subject: Re: Kernel -- GCC Version
Date: Thu, 31 Jan 2002 07:06:49 -0500 [thread overview]
Message-ID: <20020131070649.A29290@animx.eu.org> (raw)
In-Reply-To: <055301c1a9f3$af5f73e0$ed00000a@citrix.bjstuff.com> <20020130203726.B28451@animx.eu.org> <E16W7MR-0000KN-00@starship.berlin>
In-Reply-To: <E16W7MR-0000KN-00@starship.berlin>; from Daniel Phillips on Thu, Jan 31, 2002 at 03:54:03AM +0100
> > > I've looked on kernel.org, in the kernel sources, it its not really clear,
> > > from what I would see. If someone could tell me exactly what are the best
> > > and/or what Linus uses versions of gcc, etc. for compiling the different
> > > kernels? (2.0/2.2/2.4/2.5) Thanks!
> >
> > I don't recommend gcc 3.0 for kernel compiles as I had problems with it on
> > the system I tried it on.
>
> What problem exactly? I've had zero problems in the last 5 months.
I did get tons of warnings when compiling (I would assume everyone else
did). But I ignored those since it says "this is obsolete"
After booting, I had so many ECC errors (I don't recall if they were
correctable or not) that I had to give up on it.
Unless debian messedup the 3.0.3 compile it didn't work for me.
--
Lab tests show that use of micro$oft causes cancer in lab animals
next prev parent reply other threads:[~2002-01-31 11:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 1:07 Kernel -- GCC Version Ro0tSiEgE
2002-01-31 1:20 ` Arnaldo Carvalho de Melo
2002-01-31 1:21 ` Dave Jones
2002-01-31 1:25 ` Robert Love
2002-01-31 1:37 ` Wakko Warner
2002-01-31 2:54 ` Daniel Phillips
2002-01-31 3:17 ` Jeff Garzik
2002-01-31 12:06 ` Wakko Warner [this message]
2002-01-31 3:07 ` David Ford
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=20020131070649.A29290@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
--cc=ro0tsiege@bjstuff.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.