From: Scott Garman <scott.a.garman@intel.com>
To: yocto@yoctoproject.org
Subject: Re: m4 build failure - master && denzil branch
Date: Mon, 09 Jul 2012 14:05:03 -0700 [thread overview]
Message-ID: <4FFB477F.7050802@intel.com> (raw)
In-Reply-To: <4FFAEFE7.4000303@communistcode.co.uk>
On 07/09/2012 07:51 AM, Jack Mitchell wrote:
> On 09/07/12 15:37, Martin Jansa wrote:
>> On Mon, Jul 09, 2012 at 03:34:36PM +0100, Jack Mitchell wrote:
>>> So, I'm fairly sure this is a real build failure this time, again on the
>>> poky master and denzil branch.
>>>
>>> Please see attached file as the log is too big to paste.
>>
>> does your host use (e)glibc-2.16?
>>
>> if it's so, then you need this patch for m4
>> http://patchwork.openembedded.org/patch/31377/
>>
>> Cheers,
>>
>
> Yes it does, I saw this issue when building for the Rapsberry Pi the
> other day and I pulled your patches in which worked. I had assumed it
> was eglibc 2.16 on target that was causing issues not eglibc 2.16 on the
> host - hence my confusion to why the Denzil branch not building. I
> wonder if Saul looking into pulling these in soon?
As the denzil maintainer, I'm going to watch for Khem's patches to hit
master, and will have them pulled into denzil ASAP.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
prev parent reply other threads:[~2012-07-09 21:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 14:34 m4 build failure - master && denzil branch Jack Mitchell
2012-07-09 14:37 ` Martin Jansa
2012-07-09 14:51 ` Jack Mitchell
2012-07-09 14:53 ` Martin Jansa
2012-07-09 14:58 ` Jack Mitchell
2012-07-09 15:05 ` Jack Mitchell
2012-07-09 21:05 ` Scott Garman [this message]
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=4FFB477F.7050802@intel.com \
--to=scott.a.garman@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.