[oe] [PATCH] libnl: Fix possible host contamination error
Mike Looijmans
mike.looijmans at topic.nl
Wed Sep 14 11:55:28 UTC 2016
Usually this is the result from using a "cp" (typically "cp -r") command in
the install script instead of "install". Use "install" if possible, patch the
makefile if you have to. If the install script uses "cp -r", add a few extra
--preserve options to the command to prevent it overriding ownership.
On 14-09-16 12:45, Mats Karrman wrote:
> From 975b7e64462a465449d367ff6a4e5240a59221d9 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Mats=20K=C3=A4rrman?= <mats at southpole.se>
> Date: Wed, 14 Sep 2016 12:29:27 +0200
> Subject: [PATCH] libnl: Fix possible host contamination error
>
> ---
> meta/recipes-support/libnl/libnl_3.2.28.bb | 4 ++++
> 1 file changed, 4 insertions(+)
>
> Possibly a cannon to swat a fly but I get "WARNING: libnl-1_3.2.28-r0
> do_package_qa: QA Issue: libnl: /libnl-nf/usr/lib/libnl-nf-3.so.200.23.0 is
> owned by uid 1001, which is the same as the user running bitbake. This may be
> due to host contamination [host-user-contaminated]"
> type errors on every file.
>
> diff --git a/meta/recipes-support/libnl/libnl_3.2.28.bb
> b/meta/recipes-support/libnl/libnl_3.2.28.bb
> index 26982f3..3fcfbc1 100644
> --- a/meta/recipes-support/libnl/libnl_3.2.28.bb
> +++ b/meta/recipes-support/libnl/libnl_3.2.28.bb
> @@ -23,6 +23,10 @@ SRC_URI[sha256sum] =
> "cd608992c656e8f6e3ab6c1391b162a5a51c49336b9219f7f390e61fc5
>
> inherit autotools pkgconfig
>
> +do_install_append() {
> + chown -R root:root ${D}
> +}
> +
> FILES_${PN} = "${libdir}/libnl-3.so.* \
> ${libdir}/libnl.so.* \
> ${sysconfdir}"
Kind regards,
Mike Looijmans
System Expert
TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijmans at topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
Topic zoekt gedreven (embedded) software specialisten!
http://topic.nl/vacancy/topic-zoekt-technische-software-engineers/
More information about the Openembedded-devel
mailing list