From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gcc 4.8.x does not compile a working kernel for sparc
Date: Thu, 12 Jun 2014 20:46:52 +0200 [thread overview]
Message-ID: <20140612204652.4aae736f@free-electrons.com> (raw)
In-Reply-To: <20140612165138.GA12634@waldemar-brodkorb.de>
Dear Waldemar Brodkorb,
On Thu, 12 Jun 2014 18:51:38 +0200, Waldemar Brodkorb wrote:
> 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.
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> package/gcc/Config.in.host | 1 +
> 1 file changed, 1 insertion(+)
If gcc 4.8.x is indeed broken on sparc, shouldn't we completely prevent
the selection of 4.8.x on SPARC ?
Have you tested 4.9.x ?
Thanks for the report and patch!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-06-12 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 16:51 [Buildroot] [PATCH] gcc 4.8.x does not compile a working kernel for sparc Waldemar Brodkorb
2014-06-12 18:46 ` Thomas Petazzoni [this message]
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=20140612204652.4aae736f@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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