On Mon, Jul 19, 2021 at 09:37:06AM +0200, Jan Beulich wrote: > On 16.07.2021 14:38, Anthony PERARD wrote: > > +export HAS_CHECKPOLICY := $(call success,$(CHECKPOLICY) -h 2>&1 | grep -q > > xen) > > While the setting indeed gets obtained in a Makefile now, ... > > > --- a/xen/common/Kconfig > > +++ b/xen/common/Kconfig > > @@ -235,8 +235,8 @@ config XSM_FLASK_AVC_STATS > > > > config XSM_FLASK_POLICY > > bool "Compile Xen with a built-in FLASK security policy" > > - default y if "$(XEN_HAS_CHECKPOLICY)" = "y" > > - depends on XSM_FLASK > > + default y > > + depends on XSM_FLASK && "$(HAS_CHECKPOLICY)" > > ... it's still used as a Kconfig dependency. This in particular > does not address George's concern about a setting silently getting > turned off behind the back of the person having enabled it (and
This patch v2 wasn't meant to address George's concern which didn't exist at the time this v2 was sent... I was trying to address yours. But it seems that "George's concern" is part of your issues with Kconfig too, which I missed when trying to right this v2. Anyway, those two patches are the only way I'm going to try to fix the random build failure in the GitLab CI, I'm not going to try to fix issues with the use of Kconfig for now. In the mean time either v1 or v2 is committed, or will just keep getting random build failure in the GitLab CI. -- Anthony PERARD
