From: Rob Landley <rob@landley.net>
To: Shaun Ruffell <sruffell@digium.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Minimum toolchain requirements?
Date: Thu, 27 Dec 2012 21:35:27 -0600 [thread overview]
Message-ID: <1356665727.31232.15@driftwood> (raw)
In-Reply-To: <20121227200933.GC14257@digium.com> (from sruffell@digium.com on Thu Dec 27 14:09:33 2012)
On 12/27/2012 02:09:33 PM, Shaun Ruffell wrote:
> Hi Rob,
>
> On Fri, Dec 14, 2012 at 04:25:10PM -0600, Rob Landley wrote:
> > Although the README and Documentation/Changes both say the kernel
> > builds with gcc 3.2, this is no loner the case. In reality the new
> > 3.7 kernel no longer builds under unpatched gcc 4.2.1 (the last
> > GPLv2 release).
> >
> > Building for i686 breaks with
> > "arch/x86/kernel/cpu/perf_event_p6.c:22: error:
> > p6_hw_cache_event_ids causes a section type conflict" (trivial
> > workaround: patch kernel so CONFIG_BROKEN_RODATA defaults to y).
>
> I came across your email while searching for a solution to the above
> build error.
>
> In addition to setting CONFIG_BROKEN_RODATA=y, Jan Beulich sent a
> patch [1] to LKML that also fixes this build problem for me.
>
> [1] https://lkml.org/lkml/2012/11/23/308
>
> It doesn't appear to have hit Linus' tree yet though, but with luck
> someone will pick it up before 3.8 final.
>
> Cheers,
> Shaun
Having it in 3.7.x would be nice too. Copying stable.
Thanks,
Rob
next prev parent reply other threads:[~2012-12-28 3:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 22:25 Minimum toolchain requirements? Rob Landley
2012-12-27 20:09 ` Shaun Ruffell
2012-12-28 3:35 ` Rob Landley [this message]
2013-01-14 19:29 ` Greg KH
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=1356665727.31232.15@driftwood \
--to=rob@landley.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sruffell@digium.com \
--cc=stable@vger.kernel.org \
/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.