All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] gettext: Use internal libxml to avoid host contamination
Date: Wed, 20 Jul 2011 19:14:57 -0700	[thread overview]
Message-ID: <4E278BA1.5040406@mentor.com> (raw)
In-Reply-To: <4c15caba38740bfc1f30b8f0c2e0d857cb24b38b.1311213306.git.sgw@linux.intel.com>

On 07/20/2011 06:58 PM, Saul Wold wrote:
> [YOCTO #1242]
> 
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
>  meta/recipes-core/gettext/gettext_0.18.1.1.bb |    1 +
>  1 files changed, 1 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 0b11a90..e95e674 100644
> --- a/meta/recipes-core/gettext/gettext_0.18.1.1.bb
> +++ b/meta/recipes-core/gettext/gettext_0.18.1.1.bb
> @@ -32,6 +32,7 @@ EXTRA_OECONF += "--without-lispdir \
>                   --disable-native-java \
>                   --disable-openmp \
>                   --with-included-glib \
> +                 --with-included-libxml \
>                   --with-libncurses-prefix=${STAGING_LIBDIR}/.. \
>                   --without-emacs \
>                   --without-cvs \

Better than just DEPENDS libxml2 ala oe.dev?

-- 
Tom Rini
Mentor Graphics Corporation



      reply	other threads:[~2011-07-21  2:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-21  1:58 [PATCH 0/1] Fix for OpenSuse build failure Saul Wold
2011-07-21  1:58 ` [PATCH 1/1] gettext: Use internal libxml to avoid host contamination Saul Wold
2011-07-21  2:14   ` Tom Rini [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=4E278BA1.5040406@mentor.com \
    --to=tom_rini@mentor.com \
    --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.