Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Darren Hart <dvhart@linux.intel.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 21:57:39 +0000	[thread overview]
Message-ID: <1390255059.874.52.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?

Can someone share a copy of
sysroots/x86_64-linux/usr/include/guile/2.0/libguile/error.h please? I'd
like to understand what code is there triggering errors. If that line
has marcro like things in, it would be good to understand what those are
expanding to.

A config.log from a failing build would also be interesting.

Cheers,

Richard



  reply	other threads:[~2014-01-20 21:58 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 [this message]
2014-01-20 22:40               ` Darren Hart
2014-01-20 23:56             ` Richard Purdie
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=1390255059.874.52.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=dvhart@linux.intel.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