From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>
Cc: Fam Zheng <fam@euphon.net>,
qemu-trivial@nongnu.org,
"Daniel P . Berrange" <berrange@redhat.com>
Subject: Re: [PATCH] tests/docker/dockerfiles/centos: Use SDL2 instead of SDL1
Date: Wed, 21 Oct 2020 13:29:10 +0200 [thread overview]
Message-ID: <4ea997ee-a0c9-34da-8ad6-048ed4904fb3@redhat.com> (raw)
In-Reply-To: <e7ac0344-24d1-d53f-7e7f-798be452adcb@redhat.com>
On 21/10/2020 11.38, Philippe Mathieu-Daudé wrote:
> On 10/21/20 9:23 AM, Thomas Huth wrote:
>> We do not support SDL1 in QEMU anymore. Use SDL2 instead.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>> tests/docker/dockerfiles/centos7.docker | 2 +-
>> tests/docker/dockerfiles/centos8.docker | 2 +-
>> 2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/tests/docker/dockerfiles/centos7.docker
>> b/tests/docker/dockerfiles/centos7.docker
>> index 8b273725ee..6f11af1989 100644
>> --- a/tests/docker/dockerfiles/centos7.docker
>> +++ b/tests/docker/dockerfiles/centos7.docker
>> @@ -31,7 +31,7 @@ ENV PACKAGES \
>> perl-Test-Harness \
>> pixman-devel \
>> python3 \
>> - SDL-devel \
>> + SDL2-devel \
>> spice-glib-devel \
>> spice-server-devel \
>> tar \
>> diff --git a/tests/docker/dockerfiles/centos8.docker
>> b/tests/docker/dockerfiles/centos8.docker
>> index 585dfad9be..f86931f955 100644
>> --- a/tests/docker/dockerfiles/centos8.docker
>> +++ b/tests/docker/dockerfiles/centos8.docker
>> @@ -2,7 +2,7 @@ FROM centos:8.1.1911
>> RUN dnf -y update
>> ENV PACKAGES \
>> - SDL-devel \
>> + SDL2-devel \
>> bzip2 \
>> bzip2-devel \
>> dbus-daemon \
>
> I wonder if we are having docker image caching issues...
>
> build-system-centos job passed but then in check-system-centos:
>
> FAILED: libcommon.fa.p/ui_sdl2-input.c.o
> ui/sdl2.h:7:10: fatal error: SDL.h: No such file or directory
> #include
> ^~~~~~~
>
> And then in acceptance-system-centos:
>
> ./qemu-system-x86_64: error while loading shared libraries:
> libSDL2-2.0.so.0: cannot open shared object file: No such file or directory
Uh, weird, now I've got that one, too ... sorry, I only waited for the build
phase to complete before sending out the patch, I did not expect any trouble
in the testing stage...
The check-system-xxx jobs are apparently recompiling lots of files now ...
not sure yet why that happens... seems to be related to Paolo's PR from last
weekend?
The previous CI run still looks okayish:
https://gitlab.com/qemu-project/qemu/-/jobs/796502985
then the one from Paolo suddenly recompiled pretty much everything:
https://gitlab.com/qemu-project/qemu/-/jobs/796767669
Does anybody got a clue what happened here?
Thomas
next prev parent reply other threads:[~2020-10-21 11:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 7:23 [PATCH] tests/docker/dockerfiles/centos: Use SDL2 instead of SDL1 Thomas Huth
2020-10-21 8:41 ` Daniel P. Berrangé
2020-10-21 9:38 ` Philippe Mathieu-Daudé
2020-10-21 11:29 ` Thomas Huth [this message]
2020-10-21 11:37 ` Daniel P. Berrangé
2020-10-21 16:15 ` Alex Bennée
2020-10-21 10:29 ` Alex Bennée
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=4ea997ee-a0c9-34da-8ad6-048ed4904fb3@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=fam@euphon.net \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).