From: Willy Tarreau <w@1wt.eu>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch 2.4.33-rc1] updated patch kit for gcc-4.1.1
Date: Sat, 17 Jun 2006 23:38:24 +0200 [thread overview]
Message-ID: <20060617213824.GE13255@w.ods.org> (raw)
In-Reply-To: <200606172052.k5HKq5IX002958@harpo.it.uu.se>
Hi Mikael,
On Sat, Jun 17, 2006 at 10:52:05PM +0200, Mikael Pettersson wrote:
> An updated patch kit allowing gcc-4.1.1 to compile the 2.4.33-rc1 kernel is now available:
> <http://user.it.uu.se/~mikpe/linux/patches/2.4/patch-gcc4-fixes-v15-2.4.33-rc1>
>
> Changes since the previously announced version of the patch kit
> <http://marc.theaimsgroup.com/?l=linux-kernel&m=114149697417107&w=2>:
>
> - Merged the fixes for gcc-4.1 into the baseline patch kit for gcc-4.0.
> - I previously reported that gcc-4.1.0 built ppc32 kernels that oopsed
> in shrink_dcache_parent(). gcc-4.1.1 fixed this issue.
> - The architectures known to work in kernel 2.4.33-rc1 + this patch kit
> with gcc-4.1.1 and gcc-4.0.3 are i386, x86-64, and ppc32.
Thanks for still maintaining this patchset. I sometimes have coworkers
complain that they cannot build 2.4 anymore because they have let their
distro automatically upgarde gcc to 4.x. I will be able to point your
site to them. I was also thinking about updating my page on "linux
kernel useful patches" with this last update, but noticed you still have
a "patch-more-gcc4-fixes" file. Is it absolutely needed or just a cleanup ?
> /Mikael
Regards,
Willy
next prev parent reply other threads:[~2006-06-17 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-17 20:52 [patch 2.4.33-rc1] updated patch kit for gcc-4.1.1 Mikael Pettersson
2006-06-17 21:38 ` Willy Tarreau [this message]
2006-06-22 16:41 ` Adrian Bunk
2006-06-22 21:24 ` Willy Tarreau
-- strict thread matches above, loose matches on Subject: below --
2006-06-17 23:04 Mikael Pettersson
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=20060617213824.GE13255@w.ods.org \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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