From: Adrian Bunk <bunk@stusta.de>
To: Nick Warne <nick@linicks.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Has anyone had problems with GCC 4.0 and the kernel?
Date: Sat, 11 Jun 2005 21:32:22 +0200 [thread overview]
Message-ID: <20050611193222.GI3770@stusta.de> (raw)
In-Reply-To: <200506092220.12973.nick@linicks.net>
On Thu, Jun 09, 2005 at 10:20:12PM +0100, Nick Warne wrote:
> > The 2.4 kernels need fair amounts of patching,
> > 99% of which is to prevent compile-time errors. These patches
> > are not yet merged into the standard 2.4 tree and may never be.
>
> So does this mean GCC 4.x is a no-go for people still using kernel 2.4.x?
AFAIR Mikael wanted to provide his patches for compiling kernel 2.4 with
gcc 4.0 somewhere.
But they will most likely never go into into the official 2.4 kernel.
> Nick
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-06-11 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 21:20 Has anyone had problems with GCC 4.0 and the kernel? Nick Warne
2005-06-11 19:32 ` Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-09 14:21 Scott Robert Ladd
2005-06-09 14:47 ` Mikael Pettersson
2005-06-09 15:50 ` Scott Robert Ladd
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=20050611193222.GI3770@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.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