linux-yocto: fix gcc 4.6.0 compilation failures

Repeating the patch contents here, since that's the whole story:

Fixes bug: [YOCTO #1035]
Fixes bug: [YOCTO #1036]

Fixes gcc 4.6.0 compliation issues by importing the upstream change:

Author: Michal Marek <[email protected]>
Date:   Mon May 2 12:13:01 2011 +0000

kbuild: Fix passing -Wno-* options to gcc 4.4+

Starting with 4.4, gcc will happily accept -Wno-<anything> in the cc-option test and complain later when compiling a file that has some other warning. This rather unexpected behavior is intentional as per
http://gcc.gnu.org/PR28322, so work around it by testing for support of the opposite option (without the no-). Introduce a new Makefile function cc-disable-warning that does this and update two uses of cc-option in the toplevel Makefile.

:100644 100644 0ef00bd... 1d8e7e9... M  Documentation/kbuild/makefiles.txt
:100644 100644 7bd863e0.. 74bac80... M  Makefile
:100644 100644 ed2773e... ba25c44... M  scripts/Kbuild.include

Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/460
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/460

Thanks,
Bruce Ashfield <[email protected]>
---

Bruce Ashfield (2):
linux-yocto: fix gcc 4.6.0 compilation failures linux-yocto/meta-yocto: fix gcc 4.6.0 compilation failures

 .../recipes-kernel/linux/linux-yocto_git.bbappend  |   10 +++++-----
 meta/recipes-kernel/linux/linux-yocto_git.bb       |   12 ++++++------
 2 files changed, 11 insertions(+), 11 deletions(-)

Fixes gcc 4.6.0 compliation issues by importing the upstream change:

Author: Michal Marek <[email protected]>
Date: Mon May 2 12:13:01 2011 +0000

kbuild: Fix passing -Wno-* options to gcc 4.4+

Starting with 4.4, gcc will happily accept -Wno-<anything> in the cc-option test and complain later when compiling a file that has some other warning. This rather unexpected behavior is intentional as per
http://gcc.gnu.org/PR28322, so work around it by testing for support of the opposite option (without the no-). Introduce a new Makefile function cc-disable-warning that does this and update two uses of cc-option in the toplevel Makefile.

:100644 100644 0ef00bd... 1d8e7e9... M Documentation/kbuild/makefiles.txt :100644 100644 7bd863e0.. 74bac80... M Makefile
:100644 100644 ed2773e... ba25c44... M scripts/Kbuild.include

---
 .../recipes-kernel/linux/linux-yocto_git.bbappend  |   10 +++++-----
 1 files changed, 5 insertions(+), 5 deletions(-)

index 052831d..e053fe9 100644
@@ -3,11 +3,11 @@ KMACHINE_routerstationpro = "yocto/standard/routerstationpro"
 KMACHINE_mpc8315e-rdb = "yocto/standard/fsl-mpc8315e-rdb"
 KMACHINE_beagleboard = "yocto/standard/beagleboard"
 
-SRCREV_machine_emenlow = "c3bbcb676f929c4fc0511a6e66494b8770d015a1"
-SRCREV_machine_atom-pc = "b906f358fd404a1e74a961f25079274e0d933ee1"
-SRCREV_machine_routerstationpro = "95ca94d2e71ca2db6822a37a7f575fa79c3d05d0"
-SRCREV_machine_mpc8315e-rdb = "53c800c244e73d81d2832f6da306eeae3b09e5dc"
-SRCREV_machine_beagleboard = "b906f358fd404a1e74a961f25079274e0d933ee1"
+SRCREV_machine_emenlow = "5d0d346c0e4b2d837cd98dccbf043f1988e2058a"
+SRCREV_machine_atom-pc = "79d6188d99bdf63da9a0ba27c010792266e337f9"
+SRCREV_machine_routerstationpro = "d6aadb767fdcbb9886c430e90b92f49cd3a9ddcc"
+SRCREV_machine_mpc8315e-rdb = "e5c67f6a64b8b7393ca3a9c80b3ac197be0a8d5f"
+SRCREV_machine_beagleboard = "e53debfc6896bb89174ebb74154ed9b3bc72b59c"
 
 COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
 COMPATIBLE_MACHINE_routerstationpro = "routerstationpro"

1.7.0.4

From 92ad9ce8e770b46df38ed015486c76efe502f382 Mon Sep 17 00:00:00 2001
Message-Id: <92ad9ce8e770b46df38ed015486c76efe502f382.1305736112.git.bruce.ashfield@windriver.com>
In-Reply-To: <[email protected]>
References: <[email protected]>
From: Bruce Ashfield <[email protected]>
Date: Wed, 18 May 2011 12:07:44 -0400
Subject: [PATCH 1/2] linux-yocto: fix gcc 4.6.0 compilation failures

Fixes bug: [YOCTO #1035]
Fixes bug: [YOCTO #1036]

Fixes gcc 4.6.0 compliation issues by importing the upstream change:

Author: Michal Marek <[email protected]>
Date:   Mon May 2 12:13:01 2011 +0000

kbuild: Fix passing -Wno-* options to gcc 4.4+

Starting with 4.4, gcc will happily accept -Wno-<anything> in the cc-option test and complain later when compiling a file that has some other warning. This rather unexpected behavior is intentional as per
http://gcc.gnu.org/PR28322, so work around it by testing for support of the opposite option (without the no-). Introduce a new Makefile function cc-disable-warning that does this and update two uses of cc-option in the toplevel Makefile.

:100644 100644 0ef00bd... 1d8e7e9... M  Documentation/kbuild/makefiles.txt
:100644 100644 7bd863e0.. 74bac80... M  Makefile
:100644 100644 ed2773e... ba25c44... M  scripts/Kbuild.include

---
 meta/recipes-kernel/linux/linux-yocto_git.bb |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)

index 3e828c2..5c3c448 100644
@@ -14,12 +14,12 @@ KMETA = meta
 LINUX_VERSION ?= "2.6.37"
 LINUX_VERSION_EXTENSION ?= "-yocto-${LINUX_KERNEL_TYPE}"
 
-SRCREV_machine_qemuarm = "b0375c21e29453458f9aa9986dc3f1ec69bf1aef"
-SRCREV_machine_qemumips = "f5d26f2eda2be8b942172cda8f27de33ebf38ec3"
-SRCREV_machine_qemuppc = "7eb6c68d977d9039a2b5a734172b064a9d19cdc1"
-SRCREV_machine_qemux86 = "ad62d1aab734513cd96c8f4517f816420a218e77"
-SRCREV_machine_qemux86-64 = "b906f358fd404a1e74a961f25079274e0d933ee1"
-SRCREV_machine = "b906f358fd404a1e74a961f25079274e0d933ee1"
+SRCREV_machine_qemuarm = "8776b242fe2db7b4570e11496e9105b51212a446"
+SRCREV_machine_qemumips = "8f8a5e034d7e98ed871fa7ed487fbf72a79229a5"
+SRCREV_machine_qemuppc = "d9c6b3e576184f0c4223b6251c57b16ac1bac428"
+SRCREV_machine_qemux86 = "b2afed7ecd54918b73db7f30062aaaf02fdaba54"
+SRCREV_machine_qemux86-64 = "86bbbc079652d87392322fbfc14f6bd8792b0f38"
+SRCREV_machine = "0974631b821b70aee3613723ed0d4d6ba8da91c6"
 SRCREV_meta = "79669230fd82a3e7e254cf8b596a2388a4333e62"
 
 PR = "r18"

1.7.0.4

Merged into oe-core and poky as appropriate!

In the future, can you split these into 2 pull requests one for oe-core and the other for poky, it will make tracking these changes easier and one won't get lost.

Thanks
Sau!

Sure. Personally I prefer the 2 patches, one pull request, but when in Rome ...

Cheers,

Bruce

"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"