From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Thomas Huth" <thuth@redhat.com>,
qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Daniel P . Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH 4/5] tests/lcitool: Install mingw-w64-tools for the Windows cross-builds
Date: Mon, 3 Jun 2024 13:20:07 +0200 [thread overview]
Message-ID: <1cb7361a-1111-4728-bc65-81e7b328ff0e@linaro.org> (raw)
In-Reply-To: <20240601070543.37786-5-thuth@redhat.com>
On 1/6/24 09:05, Thomas Huth wrote:
> Beside g++ we also need the mingw-w64-tools for properly building
> the code in qga/vss-win32/ , so let's install that package now, too.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> tests/lcitool/projects/qemu-win-installer.yml | 1 +
> 1 file changed, 1 insertion(+)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2024-06-03 11:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-01 7:05 [PATCH 0/5] tests: Update Fedora and Alpine containers via lcitool Thomas Huth
2024-06-01 7:05 ` [PATCH 1/5] tests/lcitool: Delete obsolete centos-stream-8.yml file Thomas Huth
2024-06-03 9:32 ` Daniel P. Berrangé
2024-06-01 7:05 ` [PATCH 2/5] tests/lcitool: Bump to latest libvirt-ci and update Fedora and Alpine version Thomas Huth
2024-06-03 9:32 ` Daniel P. Berrangé
2024-06-01 7:05 ` [PATCH 3/5] .gitlab-ci.d/buildtest.yml: Use -fno-sanitize=function in the clang-system job Thomas Huth
2024-06-03 9:34 ` Daniel P. Berrangé
2024-06-01 7:05 ` [PATCH 4/5] tests/lcitool: Install mingw-w64-tools for the Windows cross-builds Thomas Huth
2024-06-03 9:34 ` Daniel P. Berrangé
2024-06-03 11:20 ` Philippe Mathieu-Daudé [this message]
2024-06-01 7:05 ` [PATCH 5/5] tests/docker/dockerfiles: Run lcitool-refresh to update Fedora and Alpine Thomas Huth
2024-06-03 9:35 ` Daniel P. Berrangé
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=1cb7361a-1111-4728-bc65-81e7b328ff0e@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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).