From: Reid Hekman <reid.hekman@ndsu.nodak.edu>
To: kelley eicher <carde@astro.umn.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: safest verion of gcc to use?
Date: 17 Jan 2002 12:39:20 -0600 [thread overview]
Message-ID: <1011292762.31205.24.camel@zeus> (raw)
In-Reply-To: <20020117121923.A7977@astro.umn.edu>
In-Reply-To: <20020117121923.A7977@astro.umn.edu>
On Thu, 2002-01-17 at 12:19, kelley eicher wrote:
> quick question here. [kernel-src]/Documentation/Changes and
> [kernel-src]/README say two different things about which version of gcc
> is recommended for the compiling of the linux kernel. README says egcs
> 1.1.2 and Documentation/Changes says to use gcc 2.95.3 or greater.
> is the last egcs release still the preferred or has that changed to the
> gcc 2.95.x releases?
Yes, Documentation/Changes is more correct. For i386, 2.95.[34] and
2.96-[>=85] work fine. GCC 3.0.3 should work too, though some drivers
have had difficulties and earlier 3.x releases generated some ICE's.
Other architectures may vary.
./README and ./Documentation/Changes need some trimming...
Regards,
Reid
next prev parent reply other threads:[~2002-01-17 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 18:19 safest verion of gcc to use? kelley eicher
2002-01-17 18:39 ` Reid Hekman [this message]
2002-01-17 19:02 ` Wakko Warner
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=1011292762.31205.24.camel@zeus \
--to=reid.hekman@ndsu.nodak.edu \
--cc=carde@astro.umn.edu \
--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 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.