From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Darren Hart <dvhart@linux.intel.com>,
Robert Yang <liezhi.yang@windriver.com>
Cc: openembedded-commits@lists.openembedded.org,
openembedded-core@lists.openembedded.org
Subject: Re: [oe-commits] Robert Yang : autogen-native: upgrade to 5.18.2
Date: Mon, 20 Jan 2014 23:56:27 +0000 [thread overview]
Message-ID: <1390262187.874.76.camel@ted> (raw)
In-Reply-To: <1390242540.3441.36.camel@dvhart-mobl4.amr.corp.intel.com>
On Mon, 2014-01-20 at 10:29 -0800, Darren Hart wrote:
> Reverting the patch allows me to move forward, but yes, I'm surprised we
> aren't seeing more build failures.... I wonder what makes us special?
For some reason I still don't have the email I can see you sent from the
list archives. What is interesting is that:
a) you have gcc 4.6, I have gcc 4.8
b) the error appears to come from error.h in SCM_NORETURN definitions
c) the config log for autogen shows different results for
"checking for working stdnoreturn.h", yes in my case, no in yours.
The definition of SCM_NORETURN is from __scm.h:
#define SCM_NORETURN __attribute__ ((noreturn))
and the dummy stdnoreturn.h that autogen would generate does:
#define noreturn _Noreturn
and then _Noreturn.h defines:
# define _Noreturn __attribute__ ((__noreturn__))
so I think what is happening is there is double macro overlap with
#define SCM_NORETURN __attribute__ ((noreturn))
becoming
#define SCM_NORETURN __attribute__ ((__attribute__ ((__noreturn__))))
How we fix it I have no idea. We should check and see if someone fixed
this upstream to start with. Robert, now we know what to look for, can
you help?
Cheers,
Richard
next prev parent reply other threads:[~2014-01-20 23:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140106112936.C3F0C50472@opal>
2014-01-09 14:42 ` [oe-commits] Robert Yang : autogen-native: upgrade to 5.18.2 Martin Jansa
2014-01-15 5:22 ` Darren Hart
2014-01-15 6:01 ` Robert Yang
2014-01-15 10:30 ` Martin Jansa
2014-01-20 13:08 ` Nick D'Ademo
2014-01-20 18:29 ` Darren Hart
2014-01-20 21:57 ` Richard Purdie
2014-01-20 22:40 ` Darren Hart
2014-01-20 23:56 ` Richard Purdie [this message]
2014-01-21 7:21 ` Robert Yang
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=1390262187.874.76.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=dvhart@linux.intel.com \
--cc=liezhi.yang@windriver.com \
--cc=openembedded-commits@lists.openembedded.org \
--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