Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Phil Blundell <philb@gnu.org>
Cc: oe-core layer <openembedded-core@lists.openembedded.org>, Patches
Subject: Re: [PATCH v2 1/1] gettext: Add depends to gettext to avoid host contamination
Date: Wed, 26 Sep 2012 12:01:16 +0100	[thread overview]
Message-ID: <1348657276.8662.96.camel@ted> (raw)
In-Reply-To: <1348583122.31293.76.camel@phil-desktop>

On Tue, 2012-09-25 at 15:25 +0100, Phil Blundell wrote:
> Can you clarify what exactly is the host contamination issue here?  I
> don't quite understand why it's appropriate for the target gettext to be
> depending on libxml2-native (which it presumably can't be linking
> against).  Also, since gettext-native is configured --with-included-xml,
> it doesn't seem as though that one is going to be using libxml2-native
> in any meaningful sense either.

I tried to unravel this a bit. I think:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=e5e6e761d15e42d94836a2153eda13bdbc4f915e

which added the --with-included-xml came later and should have removed
the DEPENDS but didn't.

(the earlier commit being
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=a0abef4533337faeb2fd991d7ab67f0a94f59568)

So this should be ok to go in and does some nice dependency unravelling.

Cheers,

Richard




      reply	other threads:[~2012-09-26 11:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-21  7:15 [PATCH v2 0/1] Fix for OpenSuse build failure Saul Wold
2011-07-21  7:15 ` [PATCH v2 1/1] gettext: Add depends to gettext to avoid host contamination Saul Wold
2012-09-25 14:25   ` Phil Blundell
2012-09-26 11:01     ` Richard Purdie [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=1348657276.8662.96.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=philb@gnu.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