On 18/01/2016 4:02 PM, Mike Looijmans wrote:
On 17-11-15 09:46, Andreas Müller wrote:
Hi,
this bugs me for a while and I wonder if I am again the only one
facing this: I get floods of warnings for sourcecode files as
WARNING: QA Issue: qtserialport:
/qtserialport-dbg/usr/src/debug/qtserialport/5.5.99+5.6.0-alpha1+gitAUTOINC+2575d33fab-r0/git/src/serialport/qserialport_p.h
is owned by uid 1000, which is the same as the user running bitbake.
This may be due to host contamination [host-user-contaminated]
WARNING: QA Issue: qtx11extras:
/qtx11extras-dbg/usr/src/debug/qtx11extras/5.5.99+5.6.0-alpha1+gitAUTOINC+d64ee96f0d-r0/git/src/x11extras/qx11info_x11.cpp
is owned by uid 1000, which is the same as the user running bitbake.
This may be due to host contamination [host-user-contaminated]
WARNING: QA Issue: qtxmlpatterns:
/qtxmlpatterns-dbg/usr/src/debug/qtxmlpatterns/5.5.99+5.6.0-alpha1+gitAUTOINC+94136d4280-r0/git/src/xmlpatterns/type/qbuiltintypes.cpp
is owned by uid 1000, which is the same as the user running bitbake.
This may be due to host contamination [host-user-contaminated]
I checked PACKAGE_DEBUG_SPLIT_STYLE is not set globally - few recipes
set PACKAGE_DEBUG_SPLIT_STYLE to debug-without-src.
Help appreciated
I got rid of these messages by doing the following replacements in do_install
and package install scripts:
Instead of "cp -r -p ..." use "cp -r --preserve=mode,links ..."
Instead of "cp -a ..." use "cp -R --no-dereference --preserve=mode,links ..."
This fixes these QA warnings in a more structured way than running a blunt "chown
root:root ..."
G'day Mike,
Was this on a recipe by recipe basis?
I've reported the following bug at
https://bugzilla.yoctoproject.org/show_bug.cgi?id=8939
But told we need to update the recipes on a recipe by recipe.
I'm still learning bitbake, yocto and angstron relationships.
So far I at a loss on where to look.
eg: getting a problem with glib-2.22 which I can only find references to in
openembedded-core.
But they suggest problem is in on of my extra layers.
--
Regards
Phil Reid
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
