From: Jack Mitchell <ml@communistcode.co.uk>
To: Saul Wold <sgw@linux.intel.com>,
openembedded-core@lists.openembedded.org
Cc: Jack Mitchell <jmitchell@cbnl.com>
Subject: Re: [oe][PATCHv2] libjson: update to 0.11 and rename to json-c
Date: Mon, 28 Oct 2013 17:30:25 +0000 [thread overview]
Message-ID: <526E9F31.2040305@communistcode.co.uk> (raw)
In-Reply-To: <5266E3C2.6040502@linux.intel.com>
On 22/10/13 21:44, Saul Wold wrote:
> On 10/21/2013 01:56 AM, Jack Mitchell wrote:
>> From: Jack Mitchell <jmitchell@cbnl.com>
>>
>> libjson is now known as json-c, it keeps support for the old
>> libjson namespace so it shouldn't break anything. Built without
>> parallel make as it would fail when it tries to link to link back
>> to itself, which is odd, but the official word is: don't build in
>> parallel.
>>
>
> Jack,
>
> Not sure what's going on yet, but I found a configure failure, see the
> attached log file.
>
> Patch review is going to be a little slower this week as RP and a
> bunch of the Yocto Project community are at Yocto Project Dev Day and
> ELC-E the rest of this week.
>
> Sau!
>
I have rebuilt this package multiple times now and have still not
managed to break it. I believe it will just be a dirty build directory,
but that shouldn't be an excuse for it not building.
Does anyone have any suggestions on how to overcome this?
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
Cambridgeshire, UK
http://www.embed.me.uk
--
next prev parent reply other threads:[~2013-10-28 17:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 8:56 [oe][PATCHv2] libjson: update to 0.11 and rename to json-c Jack Mitchell
2013-10-22 20:44 ` Saul Wold
2013-10-22 22:30 ` Jack Mitchell
2013-10-23 7:52 ` Burton, Ross
2013-10-28 17:30 ` Jack Mitchell [this message]
2013-10-28 17:49 ` Burton, Ross
2013-10-28 19:32 ` Khem Raj
2013-10-28 20:53 ` Jack Mitchell
2013-10-28 22:48 ` Khem Raj
2013-10-29 7:09 ` Martin Jansa
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=526E9F31.2040305@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=jmitchell@cbnl.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.com \
/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.