bjam calls cp directly, which can install with same user name as bitbake
in staging, which is caught by packager and reported, therefore override
cp command to use right options to make cp behave like install utility
Signed-off-by: Khem Raj <raj.k...@gmail.com>
---
meta/recipes-support/boost/boost.inc | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-support/boost/boost.inc
b/meta/recipes-support/boost/boost.inc
index e15dce4e1d..7f44638135 100644
--- a/meta/recipes-support/boost/boost.inc
+++ b/meta/recipes-support/boost/boost.inc
@@ -189,6 +189,7 @@ do_compile() {
}
do_install() {
+ export CP="cp -R --no-dereference --preserve=mode,links"
bjam ${BJAM_OPTS} \
--libdir=${D}${libdir} \
--includedir=${D}${includedir} \
--
2.25.1
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
