diff options
author | Saul Wold <sgw@linux.intel.com> | 2011-11-23 15:47:27 -0800 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-01-30 16:43:51 +0000 |
commit | df2da07184ab0a4e04e1cb273bd5bae710f5b012 (patch) | |
tree | d55f5f7e5804eeb74e3758e4d4c93dfed61a219a /meta-yocto | |
parent | 77912d65c738257c6d9b217571e25e5640d32c6f (diff) | |
download | poky-df2da07184ab0a4e04e1cb273bd5bae710f5b012.tar.gz |
intltool: remove XML::Parser check
Add Patch to disable the XML::Parser check in the target
intltool.m4, this check will find the host (not native)
XML::Parser if it's installed possibly causing Host
contamination, but will also fail configuration if XML::Parser
is not installed on the host.
Since we know that XML::Parser is installed on the image, we don't
really need this check, so comment it out.
From RP in mail thread:
> If the recipe needs perl for
> some other reason than intltool, it needs perlnative but it if only
> needs perl for intltool, we shouldn't need the dependency. The .m4 macro
> checks are well intended but don't fit the way we use perl. I really
> don't want to end up in a position where intltool automatically means we
> have to add perlnative as a dependency and we've previously seen many
> problems related to that.
(From OE-Core rev: 264fb6c5a4875cd8969a24a9f0301ed916ab827b)
(From OE-Core rev: 085c76298891dc0b0e2207ef929569672c9cb254)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta-yocto')
0 files changed, 0 insertions, 0 deletions