From: Segher Boessenkool <segher@kernel.crashing.org>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: gcc-4.2.0 breakage on powerpc?
Date: Sat, 19 May 2007 14:51:44 +0200 [thread overview]
Message-ID: <023132a5c5a4f07ec2d46b0515a55d4b@kernel.crashing.org> (raw)
In-Reply-To: <200705190953.l4J9rjO2024613@harpo.it.uu.se>
>>> and we'll end up
>>> having major kernel releases which don't build on i386 with major gcc
>>> releases, which isn't altogether desirable.
>>
>> Yeah, like 4.2.0 with powerpc. Seems like no one tested it :-(
>
> Details please. What exactly are the gcc-4.2.0 problems on powerpc?
http://gcc.gnu.org/PR31490 . Most stuff using named
sections won't build; that includes CONFIG_MODULES.
There is no viable workaround. The problem is being
handled. I'll post a patch for the kernel refusing
to build with this combination soon.
Segher
next prev parent reply other threads:[~2007-05-19 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 9:53 gcc-4.2.0 breakage on powerpc? Mikael Pettersson
2007-05-19 12:51 ` Segher Boessenkool [this message]
2007-05-19 16:11 ` Segher Boessenkool
2007-05-19 15:23 ` Clemens Koller
2007-05-19 16:13 ` Segher Boessenkool
-- strict thread matches above, loose matches on Subject: below --
2007-05-19 17:28 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=023132a5c5a4f07ec2d46b0515a55d4b@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--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