From: Thomas Huth <thuth@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
"Peter Maydell" <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
"Daniel P. Berrange" <berrange@redhat.com>,
Yonggang Luo <luoyonggang@gmail.com>
Subject: Re: egl compile error on msys CI runners
Date: Wed, 29 Mar 2023 09:23:18 +0200 [thread overview]
Message-ID: <9f745757-d5f5-e17a-a6fd-adc4db3e3fea@redhat.com> (raw)
In-Reply-To: <CAJ+F1C+6YYdNoFbraKwaw0A5NeUnwdJvrM6q98V6z0f-hr68Tw@mail.gmail.com>
On 29/03/2023 09.01, Marc-André Lureau wrote:
> Hi Peter
>
> On Tue, Mar 28, 2023 at 6:39 PM Peter Maydell <peter.maydell@linaro.org> wrote:
>>
>> 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.
>>
>
> This is an unfortunate consequence of using a fast-moving rolling
> distribution, there are random breakages. It would make sense to have
> tagged / pre-built images instead. That would also speed up the CI a
> bit, hopefully.
> Thomas, any idea how to do that?
Sorry, I've got no clue how that container stuff works on Windows :-(
Thomas
next prev parent reply other threads:[~2023-03-29 7:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 14:38 egl compile error on msys CI runners Peter Maydell
2023-03-29 7:01 ` Marc-André Lureau
2023-03-29 7:23 ` Thomas Huth [this message]
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=9f745757-d5f5-e17a-a6fd-adc4db3e3fea@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=luoyonggang@gmail.com \
--cc=marcandre.lureau@gmail.com \
--cc=peter.maydell@linaro.org \
--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).