Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH 0/2] linux-yocto: fix gcc 4.6.0 compilation failures
Date: Thu, 19 May 2011 18:05:03 -0700	[thread overview]
Message-ID: <4DD5BE3F.4010606@linux.intel.com> (raw)
In-Reply-To: <cover.1305736112.git.bruce.ashfield@windriver.com>

On 05/18/2011 09:32 AM, Bruce Ashfield wrote:
> 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<mmarek@suse.cz>
> 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.
>
>      Reported-by: Stephen Rothwell<sfr@canb.auug.org.au>
>      Signed-off-by: Michal Marek<mmarek@suse.cz>
>      Tested-by: Stephen Rothwell<sfr@canb.auug.org.au>
>      Integrated-by: Bruce Ashfield<bruce.ashfield@windriver.com>
>
> :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<bruce.ashfield@windriver.com>
> ---
>
>
> 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(-)
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
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!




  parent reply	other threads:[~2011-05-20  1:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18 16:32 [PATCH 0/2] linux-yocto: fix gcc 4.6.0 compilation failures Bruce Ashfield
2011-05-18 16:33 ` Bruce Ashfield
2011-05-18 16:33 ` [PATCH 2/2] linux-yocto/meta-yocto: " Bruce Ashfield
2011-05-20  1:05 ` Saul Wold [this message]
2011-05-20  2:25   ` [PATCH 0/2] linux-yocto: " Bruce Ashfield

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=4DD5BE3F.4010606@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=yocto@yoctoproject.org \
    /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