<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 8, 2014 at 6:51 AM, Mike Crowe <span dir="ltr"><<a href="mailto:mac@mcrowe.com" target="_blank">mac@mcrowe.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div id=":m5" class="a3s" style="overflow:hidden">The cmake recipe doesn't depend on libacl yet cmake will detect libacl.h<br>
and use it by default. This risks build failures if libacl.h is unstaged<br>
during the build and it also means that the build cmake will sometimes<br>
support ACLs and sometimes not.</div></blockquote></div><br>Is this not also a concern for the non-native recipe? And wouldn't it be better yet to use PACKAGECONFIG, rather than hardcoding the disable of acl support?<br>
-- <br>Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics
</div></div>