From: Peter Maydell <peter.maydell@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: egl compile error on msys CI runners
Date: Tue, 28 Mar 2023 15:38:14 +0100 [thread overview]
Message-ID: <CAFEAcA96hY7wxj9NjbkZmBshA6VECUQktNXAyGdS+-zLL5rWmw@mail.gmail.com> (raw)
The msys CI runners have started failing to compile with an EGL
related error:
https://gitlab.com/qemu-project/qemu/-/jobs/4015682307
In file included from
C:/GitLab-Runner/builds/qemu-project/qemu/msys64/mingw64/include/epoxy/egl.h:46,
from C:/GitLab-Runner/builds/qemu-project/qemu/include/ui/egl-helpers.h:5,
from ../ui/egl-helpers.c:21:
C:/GitLab-Runner/builds/qemu-project/qemu/msys64/mingw64/include/epoxy/egl_generated.h:11:10:
fatal error: EGL/eglplatform.h: No such file or directory
11 | #include "EGL/eglplatform.h"
| ^~~~~~~~~~~~~~~~~~~
ninja: build stopped: subcommand failed.
Dan says this is because of a msys2 packaging issue:
https://github.com/msys2/MINGW-packages/issues/16492
Can we have a meson test that doesn't try to enable EGL on systems
like this one where it's broken ? Changing the current meson.build
if cc.has_header('epoxy/egl.h', dependencies: epoxy)
to whatever the meson is for "actually try to compile with the
header" ought to do the trick, I think.
thanks
-- PMM
next reply other threads:[~2023-03-28 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 14:38 Peter Maydell [this message]
2023-03-29 7:01 ` egl compile error on msys CI runners Marc-André Lureau
2023-03-29 7:23 ` Thomas Huth
2023-03-29 8:07 ` Daniel P. Berrangé
2023-03-29 8:20 ` Thomas Huth
2023-03-29 10:22 ` Peter Maydell
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=CAFEAcA96hY7wxj9NjbkZmBshA6VECUQktNXAyGdS+-zLL5rWmw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).