From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] gcc 4.8.x does not compile a working kernel for sparc
Date: Fri, 13 Jun 2014 22:57:51 +0200 [thread overview]
Message-ID: <87ppiccysw.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20140613170047.GA10615@waldemar-brodkorb.de> (Waldemar Brodkorb's message of "Fri, 13 Jun 2014 19:00:48 +0200")
>>>>> "Waldemar" == Waldemar Brodkorb <wbx@openadk.org> writes:
> Since the switch to 4.8.x as default, the qemu-sparc target is broken.
> For a gcc bug report see here:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60624
> Switch back to gcc 4.7.x as default for sparc.
> Disable 4.8/4.9 as suggested by Thomas Petazzoni.
> I even disabled gcc snapshot, it works right now, because
> it is an old 4.8.0 snapshot by default, but as soon as this is updated
> sparc build will break.
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-06-13 20:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 17:00 [Buildroot] [PATCH v2] gcc 4.8.x does not compile a working kernel for sparc Waldemar Brodkorb
2014-06-13 20:57 ` Peter Korsgaard [this message]
2014-06-13 21:00 ` Peter Korsgaard
2014-06-14 7:15 ` Waldemar Brodkorb
2014-06-14 8:02 ` Thomas Petazzoni
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=87ppiccysw.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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