From: Adrian Bunk <bunk@fs.tum.de>
To: linux-kernel@vger.kernel.org
Cc: trivial@rustcorp.com.au
Subject: [2.5 patch] small documentation apdate regarding supported gcc versions
Date: Fri, 2 May 2003 17:57:06 +0200 [thread overview]
Message-ID: <20030502155706.GT21168@fs.tum.de> (raw)
The patch below against 2.5.68-bk11 contains a small documentation
apdate regarding supported gcc versions.
cu
Adrian
--- linux-2.5.68-bk11/README.old 2003-05-02 17:47:22.000000000 +0200
+++ linux-2.5.68-bk11/README 2003-05-02 17:48:12.000000000 +0200
@@ -152,9 +152,8 @@
COMPILING the kernel:
- - Make sure you have gcc 2.95.3 available.
- gcc 2.91.66 (egcs-1.1.2), and gcc 2.7.2.3 are known to miscompile
- some parts of the kernel, and are *no longer supported*.
+ - Make sure you have gcc >= 2.95.3 available. *gcc 2.7.2.3 and gcc 2.91.66
+ (egcs-1.1.2) are no longer supported*.
Also remember to upgrade your binutils package (for as/ld/nm and company)
if necessary. For more information, refer to ./Documentation/Changes.
--- linux-2.5.68-bk11/Documentation/Changes.old 2003-05-02 17:48:51.000000000 +0200
+++ linux-2.5.68-bk11/Documentation/Changes 2003-05-02 17:50:16.000000000 +0200
@@ -76,15 +76,13 @@
information about their gcc version requirements from another source.
The recommended compiler for the kernel is gcc 2.95.x (x >= 3), and it
-should be used when you need absolute stability. You may use gcc 3.0.x
+should be used when you need absolute stability. You may use gcc 3.x
instead if you wish, although it may cause problems. Later versions of gcc
have not received much testing for Linux kernel compilation, and there are
almost certainly bugs (mainly, but not exclusively, in the kernel) that
will need to be fixed in order to use these compilers. In any case, using
pgcc instead of plain gcc is just asking for trouble.
-gcc 2.91.66 (egcs-1.1.2) continues to be supported for SPARC64 requirements.
-
The Red Hat gcc 2.96 compiler subtree can also be used to build this tree.
You should ensure you use gcc-2.96-74 or later. gcc-2.96-54 will not build
the kernel correctly.
reply other threads:[~2003-05-02 15:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030502155706.GT21168@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@rustcorp.com.au \
/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®