From: Segher Boessenkool <segher@kernel.crashing.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Mikael Pettersson <mikpe@it.uu.se>,
lkml Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: gcc-4.2.0 breakage on powerpc?
Date: Sat, 19 May 2007 18:11:20 +0200 [thread overview]
Message-ID: <e3e772afd2f56253d20d5332499cd7ff@kernel.crashing.org> (raw)
In-Reply-To: <023132a5c5a4f07ec2d46b0515a55d4b@kernel.crashing.org>
>>>> 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.
[Cc:ing the PowerPC list]
Oh btw, most likely this is a problem on 64-bit only.
Segher
WARNING: multiple messages have this Message-ID (diff)
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Mikael Pettersson <mikpe@it.uu.se>,
lkml Mailing List <linux-kernel@vger.kernel.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: gcc-4.2.0 breakage on powerpc?
Date: Sat, 19 May 2007 18:11:20 +0200 [thread overview]
Message-ID: <e3e772afd2f56253d20d5332499cd7ff@kernel.crashing.org> (raw)
In-Reply-To: <023132a5c5a4f07ec2d46b0515a55d4b@kernel.crashing.org>
>>>> 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.
[Cc:ing the PowerPC list]
Oh btw, most likely this is a problem on 64-bit only.
Segher
next prev parent reply other threads:[~2007-05-19 16:11 UTC|newest]
Thread overview: 8+ 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
2007-05-19 16:11 ` 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
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=e3e772afd2f56253d20d5332499cd7ff@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.