summaryrefslogtreecommitdiffstats
path: root/meta/recipes-extended/sudo/sudo.inc
diff options
context:
space:
mode:
authorSaul Wold <sgw@linux.intel.com>2011-11-23 15:47:27 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-11-29 11:22:08 +0000
commitad1f3d96cfb542de3157dca6694295519c39e0bb (patch)
treeab5e0d759beea94b5cae74fb8be2c48553c2dcb9 /meta/recipes-extended/sudo/sudo.inc
parentc06eecfc8480e847919125df14302a25ebd474b4 (diff)
downloadpoky-ad1f3d96cfb542de3157dca6694295519c39e0bb.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) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-extended/sudo/sudo.inc')
0 files changed, 0 insertions, 0 deletions