From: Alvaro Figueroa <fede2@fuerzag.ulatina.ac.cr>
To: LKML <linux-kernel@vger.kernel.org>
Cc: "David S. Miller" <davem@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: linux-2.5.7
Date: 04 Apr 2002 08:45:10 -0600 [thread overview]
Message-ID: <1017931510.1567.4.camel@lucy> (raw)
In-Reply-To: <20020404014223.A22363@twiddle.net>
> Rather, "the ancient version of gcc commonly used on sparc64".
I'm sort of forwading a message I wrote at March 13th that was never
answered and that I think has a huge priority for the sparc64 port.
--
> GCC 3.0.3 works.
>
> (Dave S. Miller wrote)
> I won't accept kernel bug reports for people using it though.
> The old egcs64 compiler is the only thing I trust right now, still.
In that case, I would repectfully comment that a special case comment
should be added to the lkml FAQ (chapter 8, section 2), because there,
it is stated:
"
2. What are the recommended compiler/binutils for building kernels?
* (REG) This depends on the kernel version. Until 26-OCT-2000, gcc
2.7.2.3 was the recommended compiler for all kernels. On this date,
Linus announced that gcc 2.91.66 (aka egcs 1.1.2) is the recommended
compiler for 2.4.x kernels up to version 2.4.9. Gcc 2.95.3 is the
recommended compiler for kernel 2.4.10 and later.
(...)
Always see the Documentation/Changes file for details.
"
At Documentation/Changes you can read some negative comments about this
version of the compiler, and it even says that is likely that 2.5 will
drop egcs workarrounds.
How will this be managed? What is the recommended compiler for 2.5?
--
Alvaro Figueroa
next prev parent reply other threads:[~2002-04-04 14:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-30 23:23 linux-2.5.7 Timothy Murphy
2002-03-30 23:41 ` linux-2.5.7 Alexander Viro
2002-03-31 2:22 ` linux-2.5.7 David S. Miller
2002-03-31 7:54 ` linux-2.5.7 Alexander Viro
2002-03-31 8:30 ` linux-2.5.7 Andrew Morton
2002-03-31 8:42 ` linux-2.5.7 Alexander Viro
2002-04-04 9:42 ` linux-2.5.7 Richard Henderson
2002-04-04 14:45 ` Alvaro Figueroa [this message]
2002-03-31 3:25 ` linux-2.5.7 Pierre Rousselet
2002-03-31 6:21 ` linux-2.5.7 David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2002-03-30 23:48 linux-2.5.7 Neil Brown
2002-03-31 0:02 ` linux-2.5.7 Keith Owens
2002-03-31 2:04 ` linux-2.5.7 Alexander Viro
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=1017931510.1567.4.camel@lucy \
--to=fede2@fuerzag.ulatina.ac.cr \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
/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