From: Mikael Pettersson <mikpe@csd.uu.se>
To: Scott Robert Ladd <lkml@coyotegulch.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Has anyone had problems with GCC 4.0 and the kernel?
Date: Thu, 9 Jun 2005 16:47:16 +0200 [thread overview]
Message-ID: <17064.22132.219886.207366@alkaid.it.uu.se> (raw)
In-Reply-To: <42A85065.4000108@coyotegulch.com>
Scott Robert Ladd writes:
> Hello,
>
> I've had several inquiries recently in regard to compiling the kernel
> with GCC 4.0. It seems folk are having problems, do a Google search, and
> find my capsule review of GCC 4.0 at:
>
> http://www.coyotegulch.com/reviews/gcc4/index.html
>
> I'm not running a GCC 4.0-created kernel, but I had no problems
> compiling it and running one a few weeks ago. Before I start looking
> into this further, has anyone here had problems with GCC 4? Maybe I just
> hallucinated that it compiled and booted... ;)
gcc-4.0.0 vanilla is broken and miscompiles some ipv4/sysctl stuff.
More recent 4.0.1 snapshots are OK.
I've been using gcc4 for 2.6 and 2.4 kernels since late January,
for both desktops and servers, and for i386/x86-64/ppc/ppc64.
Recent 2.6 kernels should work as-is, except perhaps in poorly
maintained drivers. 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.
next prev parent reply other threads:[~2005-06-09 14:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 14:21 Scott Robert Ladd
2005-06-09 14:47 ` Mikael Pettersson [this message]
2005-06-09 15:50 ` Scott Robert Ladd
2005-06-09 21:20 Nick Warne
2005-06-11 19:32 ` 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=17064.22132.219886.207366@alkaid.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@coyotegulch.com \
/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
all inboxes | Powered by JetHome®