From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: meta-virtualization@lists.yoctoproject.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: xen-4.17 build failure (av_permissions.h: No such file or directory)
Date: Thu, 19 Jan 2023 14:22:02 +0100 [thread overview]
Message-ID: <20230119142202.594f36c9@booty> (raw)
Hello Bruce,
we had this failure on the xen recipe during an AB meta-virt build:
| In file included from xsm/flask/ss/services.c:46:
| ./xsm/flask/include/avc.h:18:10: fatal error: av_permissions.h: No
such file or directory | 18 | #include "av_permissions.h"
| | ^~~~~~~~~~~~~~~~~~
See:
https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/1168/steps/17/logs/stdio
According to Alex's analysis it appears to be a race condition in the
xen makefile.
Could you check that?
Best regards,
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next reply other threads:[~2023-01-19 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 13:22 Luca Ceresoli [this message]
2023-01-19 13:52 ` xen-4.17 build failure (av_permissions.h: No such file or directory) Bruce Ashfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230119142202.594f36c9@booty \
--to=luca.ceresoli@bootlin.com \
--cc=alexandre.belloni@bootlin.com \
--cc=bruce.ashfield@gmail.com \
--cc=meta-virtualization@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.