From: Nicholas Knight <tegeran@home.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.10-pre5
Date: Sat, 8 Sep 2001 01:19:38 -0700 [thread overview]
Message-ID: <01090801193801.00271@c779218-a> (raw)
In-Reply-To: <3B99A8C2.56E88CE3@isn.net> <003001c1382d$f483d9d0$010da8c0@uglypunk> <20010908014643.A846@home.com>
In-Reply-To: <20010908014643.A846@home.com>
On Friday 07 September 2001 11:46 pm, Josh McKinney wrote:
> On approximately Sat, Sep 08, 2001 at 03:44:31PM +0930, Kingsley
Foreman wrote:
> > Yes i got this too
> > anyone got a fix
>
> Don't use gcc-3.0
Excuse me, but shouldn't it be a goal to have the kernel compiling
cleanly on gcc-3.0 as soon as is reasonable?
Telling people to use older versions of GCC for the kernel is not really
a "good" thing if it can be avoided.
Personaly I don't use gcc-3.0 yet, but some do, and many will follow, and
when they do, it'd be nice to have the kernel compiling cleanly, would it
not?
They want a fix, not a one-line editorial. They're reporting a "bug", so
that it may be fixed.
next prev parent reply other threads:[~2001-09-08 8:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-08 5:12 2.4.10-pre5 Garst R. Reese
2001-09-08 6:14 ` 2.4.10-pre5 Kingsley Foreman
2001-09-08 6:46 ` 2.4.10-pre5 Josh McKinney
2001-09-08 8:19 ` Nicholas Knight [this message]
2001-09-08 9:32 ` 2.4.10-pre5 Eyal Lebedinsky
2001-09-08 13:05 ` 2.4.10-pre5 Alan Cox
2001-09-08 22:03 ` 2.4.10-pre5 Alessandro Suardi
2001-09-09 4:05 ` 2.4.10-pre5 Josh McKinney
2001-09-09 4:14 ` 2.4.10-pre5 Steven Walter
2001-09-09 11:48 ` 2.4.10-pre5 (and gcc-3) Ken Moffat
2001-09-09 21:22 ` compiling kernel with gcc-3 (was: 2.4.10-pre5) Alessandro Suardi
2001-09-08 10:36 ` 2.4.10-pre5 Peter Osterlund
2001-09-08 12:57 ` 2.4.10-pre5 Garst R. Reese
2001-09-09 5:30 ` 2.4.10-pre5/pre6 Garst R. Reese
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=01090801193801.00271@c779218-a \
--to=tegeran@home.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox