All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] gettext: use included libxml and libcroco
Date: Sat, 3 Sep 2011 20:27:31 +0200	[thread overview]
Message-ID: <7B379123-8667-42B3-B2F7-96CBBB02D2C7@dominion.thruhere.net> (raw)
In-Reply-To: <93299d9dce4bdc3acf75026edf0356b287b0c6f9.1315069299.git.sgw@linux.intel.com>


Op 3 sep. 2011, om 19:04 heeft Saul Wold het volgende geschreven:

> [YOCTO #1400]
> 
> By using the included libxml and libcroco, we do not create additional
> on this core library. There was an ordering issue that when one library
> was not built, but gettext detected the other library a compliation would
> fail, this will force it to always use the included libraries.
> 
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
> meta/recipes-core/gettext/gettext_0.18.1.1.bb |    2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/meta/recipes-core/gettext/gettext_0.18.1.1.bb b/meta/recipes-core/gettext/gettext_0.18.1.1.bb
> index 9ec851e..0bcd90b 100644
> --- a/meta/recipes-core/gettext/gettext_0.18.1.1.bb
> +++ b/meta/recipes-core/gettext/gettext_0.18.1.1.bb
> @@ -36,6 +36,8 @@ EXTRA_OECONF += "--without-lispdir \
>                  --without-emacs \
>                  --without-cvs \
>                  --without-git \
> +                 --with-included-libxml \
> +                 --with-included-libcroco \
>                 "

That's missing a PR bump


  reply	other threads:[~2011-09-03 18:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-03 17:04 [PATCH 0/1] Fix gettext dependency issue Saul Wold
2011-09-03 17:04 ` [PATCH 1/1] gettext: use included libxml and libcroco Saul Wold
2011-09-03 18:27   ` Koen Kooi [this message]
2011-09-08  3:42 ` [PATCH 0/1] Fix gettext dependency issue Saul Wold

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=7B379123-8667-42B3-B2F7-96CBBB02D2C7@dominion.thruhere.net \
    --to=koen@dominion.thruhere.net \
    --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 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.