Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/7] elfutils: fix builds with gcc 4.6
Date: Tue, 05 Apr 2011 17:46:24 +0100	[thread overview]
Message-ID: <1302021985.2511.16.camel@scimitar> (raw)
In-Reply-To: <4D9A772C.4070409@gmail.com>

On Mon, 2011-04-04 at 18:58 -0700, Khem Raj wrote:
> On 4/1/2011 6:51 AM, Joshua Lock wrote:
> > From: Joshua Lock<josh@linux.intel.com>
> >
> > gcc 4.6 (as used in Fedora 15) adds some extra warnings which are
> > included with Werror. The new unused-but-set variable warning causes
> > an error in libasm of elfutils. Work around this by removing
> > unused-but-set from Werror.
> >
> > Signed-off-by: Joshua Lock<josh@linux.intel.com>
> > ---
> >   meta/recipes-devtools/elfutils/elfutils_0.148.bb |    4 ++++
> >   1 files changed, 4 insertions(+), 0 deletions(-)
> >
> > diff --git a/meta/recipes-devtools/elfutils/elfutils_0.148.bb b/meta/recipes-devtools/elfutils/elfutils_0.148.bb
> > index b2f700e..c395be8 100644
> > --- a/meta/recipes-devtools/elfutils/elfutils_0.148.bb
> > +++ b/meta/recipes-devtools/elfutils/elfutils_0.148.bb
> > @@ -40,6 +40,10 @@ SRC_URI += "\
> >
> >   inherit autotools
> >
> > +# GCC 4.6.0 raises an unused-but-set warning in libasm, for now remove
> > +# this warning from Werror
> > +CFLAGS_virtclass-native += "-Wno-error=unused-but-set-variable"
> > +
> 
> unused-but-set-variable is a new option in gcc 4.6 which means this will 
> cause problems with older gcc's as they wont recognize this option and 
> not all distros have gcc 4.6
> as base compiler. Have you tried compiling this patchset on a build 
> machine which has older gcc ? say 4.5

I had not but thanks for pointing this out. I'll work up a new patch and
make sure to test it on a machine with an older GCC.

Cheers,
Joshua
-- 
Joshua Lock
        Yocto Build System Monkey
        Intel Open Source Technology Centre




  parent reply	other threads:[~2011-04-05 16:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-01 13:51 [PATCH 0/7] Fedora 15 and GCC 4.6 compatability patches Joshua Lock
2011-04-01 13:51 ` [PATCH 1/7] elfutils: fix builds with gcc 4.6 Joshua Lock
2011-04-05  1:58   ` Khem Raj
2011-04-05  2:38     ` Khem Raj
2011-04-05 16:46     ` Joshua Lock [this message]
2011-04-05 17:03       ` Khem Raj
2011-04-06 11:05         ` Joshua Lock
2011-04-01 13:51 ` [PATCH 2/7] python-native: add missing SRC_URI hashes Joshua Lock
2011-04-01 13:52 ` [PATCH 3/7] libx11: " Joshua Lock
2011-04-01 13:52 ` [PATCH 4/7] xorg-[lib-common|proto-common]: disable use of fop document generation Joshua Lock
2011-04-01 13:52 ` [PATCH 5/7] libx11: disable building of specs Joshua Lock
2011-04-01 13:52 ` [PATCH 6/7] openjade: fix build with GCC 4.6 Joshua Lock
2011-04-01 13:52 ` [PATCH 7/7] xserver-xf86: explicitly disable fop document generation Joshua Lock
2011-04-04 12:56 ` [PATCH 0/7] Fedora 15 and GCC 4.6 compatability patches Richard Purdie

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=1302021985.2511.16.camel@scimitar \
    --to=josh@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.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