From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Russell King <rmk@arm.linux.org.uk>, linux-kernel@vger.kernel.org
Subject: [2.6 patch] Documentation/arm/README: small update
Date: Wed, 2 Nov 2005 19:34:15 +0100 [thread overview]
Message-ID: <20051102183415.GF4272@stusta.de> (raw)
- egcs is not supported by kernel 2.6
- gcc 3.3 seems to be a good choice on ARM
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
This patch was already sent on:
- 3 Sep 2005
--- linux-2.6.13-mm1-full/Documentation/arm/README.old 2005-09-03 00:02:55.000000000 +0200
+++ linux-2.6.13-mm1-full/Documentation/arm/README 2005-09-03 00:03:51.000000000 +0200
@@ -8,10 +8,9 @@
---------------------
In order to compile ARM Linux, you will need a compiler capable of
- generating ARM ELF code with GNU extensions. GCC 2.95.1, EGCS
- 1.1.2, and GCC 3.3 are known to be good compilers. Fortunately, you
- needn't guess. The kernel will report an error if your compiler is
- a recognized offender.
+ generating ARM ELF code with GNU extensions. GCC 3.3 is known to be
+ a good compiler. Fortunately, you needn't guess. The kernel will report
+ an error if your compiler is a recognized offender.
To build ARM Linux natively, you shouldn't have to alter the ARCH = line
in the top level Makefile. However, if you don't have the ARM Linux ELF
next reply other threads:[~2005-11-02 18:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 18:34 Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-24 10:36 [2.6 patch] Documentation/arm/README: small update Adrian Bunk
2005-08-28 17:17 ` Russell King
2005-09-02 22:19 ` Adrian Bunk
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=20051102183415.GF4272@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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