The autobuilder run over the weekend failed in the non-GPLv3 buildset on coreutils: /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-non-gpl3/build/build/tmp/work/i586-poky-linux/coreutils/6.9-r5/coreutils-6.9/lib/acl-internal.h:29:25: fatal error: acl/libacl.h: No such file or directory http://errors.yoctoproject.org/Errors/Details/26652/ I've manage to replicate this locally, the problem is that the acl PACKAGECONFIG doesn't set enough variables so it isn't deterministic: if acl is installed but the PACKAGECONFIG is disabled it still decides that libacl should be used. You're then open to the race of acl being removed from the sysroot even though coreutils wants to link to it. As Wind River tend to care about the no-GPLv3 option and you're listed as the maintainer of coreutils, would you be able to look into this?
Just noticed this bug. I'll look into it ASAP. // Qi
commit fad63e3ab42d03f0802e8d772b3d28ba9e704ced Author: Chen Qi <Qi.Chen@windriver.com> Date: Tue Feb 16 15:06:05 2016 +0800 coreutils: fix problem with acl for 6.9 version If 'acl' is not in DISTRO_FEATURES, building coreutils 6.9 would sometimes fail. The problem could be reproduced by executing the following command. `bitbake acl && bitbake coreutils -c configure && bitbake acl -c cleansstate && bitbake coreutils -c compile' Fix this problem by setting the correct value for the 'acl' PACKAGECONFIG. [YOCTO #8906] (From OE-Core rev: a9004ff3f8de83d22d9159a9f103e2773e927a0b) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Not reproducible running `bitbake acl && bitbake coreutils -c configure && bitbake acl -c cleansstate && bitbake coreutils -c compile' on "master:f7b520878babbaa7527151f22c031ae160512753"