From: "Barry K. Nathan" <barryn@pobox.com>
To: reaster@comptechnews.com (Robert B. Easter)
Cc: linux-kernel@vger.kernel.org
Subject: Re: recommended gcc compiler version
Date: Thu, 21 Dec 2000 23:00:46 -0800 (PST) [thread overview]
Message-ID: <200012220700.XAA09901@pobox.com> (raw)
In-Reply-To: <0012212320430F.02217@comptechnews> from "Robert B. Easter" at Dec 21, 2000 11:20:43 PM
Robert B. Easter wrote:
> This is a newbie question, but what are the recommended gcc compiler versions
> for compiling,
This is discussed in the Documentation/Changes file, in a given kernel's
source. Brief summaries follow (which assume you're using an x86 CPU).
> Linux 2.2.18?
gcc 2.7.2.3 is safest, but egcs 1.1.2 should be safe even for
mission-critical stuff. gcc 2.95.2 seems to work for many people, but
isn't necessarily safe.
> Linux 2.4.0?
egcs 1.1.2 is the safe choice, but gcc 2.95.2 seems to work. gcc 2.7.2.3
miscompiles 2.4 more often than not, so 2.4 has a preprocessor check that
stops any attempts to compile it with 2.7.2.3.
-Barry K. Nathan <barryn@pobox.com>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-22 7:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-22 4:20 recommended gcc compiler version Robert B. Easter
2000-12-22 6:19 ` Matthew D. Pitts
2000-12-22 7:08 ` Tim Wright
2000-12-22 19:17 ` Linus Torvalds
2000-12-23 15:55 ` Matthew Vanecek
2000-12-22 7:00 ` Barry K. Nathan [this message]
2000-12-22 18:09 ` Andreas Dilger
2000-12-22 8:51 ` Alan Cox
2000-12-22 10:54 ` Rogier Wolff
2000-12-22 11:53 ` Anuradha Ratnaweera
2000-12-24 9:14 ` Kai Henningsen
2000-12-26 8:06 ` Anuradha Ratnaweera
2000-12-22 19:25 ` Linus Torvalds
2000-12-22 20:11 ` Andi Kleen
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=200012220700.XAA09901@pobox.com \
--to=barryn@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reaster@comptechnews.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