From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] qemu-sparc: use default gcc
Date: Sun, 21 Sep 2014 19:39:57 +0200 [thread overview]
Message-ID: <20140921193957.77da49d4@free-electrons.com> (raw)
In-Reply-To: <20140919103404.GA24103@waldemar-brodkorb.de>
Dear Waldemar Brodkorb,
On Fri, 19 Sep 2014 12:34:04 +0200, Waldemar Brodkorb wrote:
> With the kernel patch from:
> http://patchwork.ozlabs.org/patch/384285/
> There is no problem with latest gcc anymore.
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> .../linux/linux-0001-sparc-memset-fix.patch | 50 ++++++++++++++++++++
> configs/qemu_sparc_ss10_defconfig | 2 +
> package/gcc/Config.in.host | 7 ++-
> 3 files changed, 55 insertions(+), 4 deletions(-)
> create mode 100644 board/qemu/sparc-ss10/linux/linux-0001-sparc-memset-fix.patch
It's a bit annoying that we need a patch to the kernel to make sure
that gcc can build a working kernel since it means that people not
using the Qemu defconfig for SPARC builds will not get the patch.
Though the problem has been around since a long time, so if people
really bothered about working SPARC support in upstream kernel/gcc,
they should have complained earlier.
So: applied, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-09-21 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 10:34 [Buildroot] [PATCH 2/2] qemu-sparc: use default gcc Waldemar Brodkorb
2014-09-21 17:39 ` Thomas Petazzoni [this message]
2014-09-21 19:32 ` Waldemar Brodkorb
2014-09-21 19:45 ` Thomas Petazzoni
2014-09-21 19:50 ` Waldemar Brodkorb
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=20140921193957.77da49d4@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 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.