From: Dave Jones <davej@suse.de>
To: Ro0tSiEgE <ro0tsiege@bjstuff.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel -- GCC Version
Date: Thu, 31 Jan 2002 02:21:27 +0100 [thread overview]
Message-ID: <20020131022127.C31313@suse.de> (raw)
In-Reply-To: <055301c1a9f3$af5f73e0$ed00000a@citrix.bjstuff.com>
In-Reply-To: <055301c1a9f3$af5f73e0$ed00000a@citrix.bjstuff.com>; from ro0tsiege@bjstuff.com on Wed, Jan 30, 2002 at 07:07:42PM -0600
On Wed, Jan 30, 2002 at 07:07:42PM -0600, Ro0tSiEgE wrote:
> 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!
Top level README has this info, as does the Documentation/Changes file.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-01-31 1:24 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 [this message]
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
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=20020131022127.C31313@suse.de \
--to=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox