Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v2 1/3] libplist: issues with parallel make so disable
Date: Wed, 05 Sep 2012 16:40:41 +0200	[thread overview]
Message-ID: <k27o8p$c19$1@ger.gmane.org> (raw)
In-Reply-To: <1346855574-1528-1-git-send-email-ml@communistcode.co.uk>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 05-09-12 16:32, ml@communistcode.co.uk schreef:
> From: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>
> 
> Signed-off-by: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk> --- 
> meta-oe/recipes-extended/libimobiledevice/libplist_1.8.bb | 2 ++ 1 file
> changed, 2 insertions(+)
> 
> diff --git a/meta-oe/recipes-extended/libimobiledevice/libplist_1.8.bb
> b/meta-oe/recipes-extended/libimobiledevice/libplist_1.8.bb index
> 9c218fb..5356431 100644 ---
> a/meta-oe/recipes-extended/libimobiledevice/libplist_1.8.bb +++
> b/meta-oe/recipes-extended/libimobiledevice/libplist_1.8.bb @@ -6,6 +6,8
> @@ LIC_FILES_CHKSUM =
> "file://COPYING;md5=ebb5c50ab7cab4baeffba14977030c07 \
> 
> DEPENDS = "libxml2 glib-2.0 swig python"
> 
> +PARALLEL_MAKE = ""

FWIW, there's a one-liner commit in upstream git to fix the libcnary problem

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFQR2RpMkyGM64RGpERAj9fAJ4rqWHvYnNibjNuve9c0saIxDQswQCgswm/
/7MxaXHJvjEnjLxcsoSJRS4=
=aHz3
-----END PGP SIGNATURE-----




      parent reply	other threads:[~2012-09-05 14:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-05 14:32 [PATCH v2 1/3] libplist: issues with parallel make so disable ml
2012-09-05 14:32 ` [PATCH v2 2/3] liblockdev: new recipe, new version of libcec requires it ml
2012-09-05 15:12   ` Burton, Ross
2012-09-05 14:32 ` [PATCH v2 3/3] libcec: update libcec to latest version (1.8.1) as to include RasPi support ml
2012-09-05 14:40 ` Koen Kooi [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='k27o8p$c19$1@ger.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --cc=openembedded-devel@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