<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 20, 2015 at 4:02 AM, Max Krummenacher <span dir="ltr"><<a href="mailto:max.oss.09@gmail.com" target="_blank">max.oss.09@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Am Dienstag, den 17.11.2015, 09:46 +0100 schrieb Andreas Müller:<br>
> Hi,<br>
><br>
> this bugs me for a while and I wonder if I am again the only one<br>
> facing this: I get floods of warnings for sourcecode files as<br>
><br>
> WARNING: QA Issue: qtserialport:<br>
> /qtserialport-dbg/usr/src/debug/qtserialport/5.5.99+5.6.0-alpha1<br>
+gitAUTOINC+2575d33fab-r0/git/src/serialport/qserialport_p.h<br>
> is owned by uid 1000, which is the same as the user running bitbake.<br>
> This may be due to host contamination [host-user-contaminated]<br>
> WARNING: QA Issue: qtx11extras:<br>
> /qtx11extras-dbg/usr/src/debug/qtx11extras/5.5.99+5.6.0-alpha1<br>
+gitAUTOINC+d64ee96f0d-r0/git/src/x11extras/qx11info_x11.cpp<br>
> is owned by uid 1000, which is the same as the user running bitbake.<br>
> This may be due to host contamination [host-user-contaminated]<br>
> WARNING: QA Issue: qtxmlpatterns:<br>
> /qtxmlpatterns-dbg/usr/src/debug/qtxmlpatterns/5.5.99+5.6.0-alpha1<br>
+gitAUTOINC+94136d4280-r0/git/src/xmlpatterns/type/qbuiltintypes.cpp<br>
> is owned by uid 1000, which is the same as the user running bitbake.<br>
> This may be due to host contamination [host-user-contaminated]<br>
><br>
> I checked PACKAGE_DEBUG_SPLIT_STYLE is not set globally - few recipes<br>
> set PACKAGE_DEBUG_SPLIT_STYLE to debug-without-src.<br>
><br>
> Help appreciated<br>
><br>
> Andreas<br>
<br>
</span>I see this also in my builds. The warnings clutter the build output in a<br>
way that makes the warnings mostly useless. Who will spot the one<br>
important new warning in the hundreds of host-user-contaminated ones?<br>
A fresh build of core-image-minimal today gave me 54 of these warnings.<br>
All but one (glibc-locale) complaining on source files.<br>
<br>
I checked a few recipes and most of them were not even using a custom<br>
do_install but autotools generated 'make install' with something like<br>
'cp -p src/* dest/' or so.<br></blockquote><div><br></div><div>Yes, this is the most common case. Usage of cp -a or cp -p means the build ownership is retained, and no chown is run to fix it. <br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Even if I know how to do it I think we should not patch upstream sources<br>
to suppress a warning introduced by the downstream build system with<br>
loads of false positives and then have to maintain the patches as<br>
upstream is progressing.<br></blockquote><div><br></div><div>Either we're calling the upstream buildsystem and not running cp directly, in which case it's a bug in the upstream buildsystem, since make install will result in non-deterministic behavior in the ownership of the installed files, or it's a cp -a case, which doesn't require altering upstream with a patch at all, only recipe modification.<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I haven't looked into how one does it but I'm inclined to switch of the<br>
warning globally, e.g. in local.conf.</blockquote></div><br></div><div class="gmail_extra">Blindly disabling them will just result in ignoring a problem. Files in the target filesystem are owned by your build user, who most likely doesn't even exist on target.<br>-- <br><div class="gmail_signature">Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics</div>
</div></div>