[2/2] qemu-sparc: use default gcc

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

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

Hi,
Thomas Petazzoni wrote,

> 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.

The patch was accepted by David Miller, so the problem shouldn't
exist in the next version of the Kernel.

If buildroot would have a global Linux patch directory, something
like this could be added meanwhile.

best regards
 Waldemar

Dear Waldemar Brodkorb,

On Sun, 21 Sep 2014 21:32:51 +0200, Waldemar Brodkorb wrote:

> > 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.
> 
> The patch was accepted by David Miller, so the problem shouldn't
> exist in the next version of the Kernel.

Yes, I know, but it leaves earlier kernel versions broken, at least out
of the box.

> If buildroot would have a global Linux patch directory, something
> like this could be added meanwhile.

This clearly something that we do not want to do. See
https://dev.openwrt.org/browser/trunk/target/linux/generic/patches-3.14,
and you'll discover why we clearly don't want to do that. My colleague
Maxime has just spent several painful days to bump the 3.14 OpenWRT
stack of kernel patches to 3.16, just for the sake of being able to run
OpenWRT on a 3.16 kernel. It's just ridiculous, and that's not a
situation where we want Buildroot to be.

Best regards,

Thomas

Hi Thomas,
Thomas Petazzoni wrote,

> Dear Waldemar Brodkorb,
> 
> On Sun, 21 Sep 2014 21:32:51 +0200, Waldemar Brodkorb wrote:
> 
> > > 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.
> > 
> > The patch was accepted by David Miller, so the problem shouldn't
> > exist in the next version of the Kernel.
> 
> Yes, I know, but it leaves earlier kernel versions broken, at least out
> of the box.
> 
> > If buildroot would have a global Linux patch directory, something
> > like this could be added meanwhile.
> 
> This clearly something that we do not want to do. See
> https://dev.openwrt.org/browser/trunk/target/linux/generic/patches-3.14,
> and you'll discover why we clearly don't want to do that. My colleague
> Maxime has just spent several painful days to bump the 3.14 OpenWRT
> stack of kernel patches to 3.16, just for the sake of being able to run
> OpenWRT on a 3.16 kernel. It's just ridiculous, and that's not a
> situation where we want Buildroot to be.

Sure, I don't want that you misuse the ability for having generic
Linux kernel patches, like the OpenWrt devs do ;)

Just maybe some minimal stuff, which is queued for upstream
inclusion. But hey, it is okay for me when you don't want to start
with it.

best regards
 Waldemar