qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [PATCH for-10.1] CI: Use mingw-w64-x86_64-curl-winssl instead of mingw-w64-x86_64-curl for Windows build
@ 2025-08-06 20:09 Stefan Weil via
  2025-08-06 20:27 ` Pierrick Bouvier
  0 siblings, 1 reply; 4+ messages in thread
From: Stefan Weil via @ 2025-08-06 20:09 UTC (permalink / raw)
  To: Yonggang Luo, Alex Bennée, Philippe Mathieu-Daudé,
	Thomas Huth
  Cc: qemu-devel, Stefan Weil

mingw-w64-x86_64-curl-winssl is required for https connections.

Signed-off-by: Stefan Weil <sw@weilnetz.de>
---
 .gitlab-ci.d/windows.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.gitlab-ci.d/windows.yml b/.gitlab-ci.d/windows.yml
index 45ed0c96fe..beac39e5bd 100644
--- a/.gitlab-ci.d/windows.yml
+++ b/.gitlab-ci.d/windows.yml
@@ -77,7 +77,7 @@ msys2-64bit:
       git grep make sed
       mingw-w64-x86_64-binutils
       mingw-w64-x86_64-ccache
-      mingw-w64-x86_64-curl
+      mingw-w64-x86_64-curl-winssl
       mingw-w64-x86_64-gcc
       mingw-w64-x86_64-glib2
       mingw-w64-x86_64-libnfs
-- 
2.47.2



^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [PATCH for-10.1] CI: Use mingw-w64-x86_64-curl-winssl instead of mingw-w64-x86_64-curl for Windows build
  2025-08-06 20:09 Stefan Weil via
@ 2025-08-06 20:27 ` Pierrick Bouvier
  0 siblings, 0 replies; 4+ messages in thread
From: Pierrick Bouvier @ 2025-08-06 20:27 UTC (permalink / raw)
  To: Stefan Weil, Yonggang Luo, Alex Bennée,
	Philippe Mathieu-Daudé, Thomas Huth
  Cc: qemu-devel

On 8/6/25 1:09 PM, Stefan Weil via wrote:
> mingw-w64-x86_64-curl-winssl is required for https connections.
> 
> Signed-off-by: Stefan Weil <sw@weilnetz.de>
> ---
>   .gitlab-ci.d/windows.yml | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/.gitlab-ci.d/windows.yml b/.gitlab-ci.d/windows.yml
> index 45ed0c96fe..beac39e5bd 100644
> --- a/.gitlab-ci.d/windows.yml
> +++ b/.gitlab-ci.d/windows.yml
> @@ -77,7 +77,7 @@ msys2-64bit:
>         git grep make sed
>         mingw-w64-x86_64-binutils
>         mingw-w64-x86_64-ccache
> -      mingw-w64-x86_64-curl
> +      mingw-w64-x86_64-curl-winssl
>         mingw-w64-x86_64-gcc
>         mingw-w64-x86_64-glib2
>         mingw-w64-x86_64-libnfs

Reviewed-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH for-10.1] CI: Use mingw-w64-x86_64-curl-winssl instead of mingw-w64-x86_64-curl for Windows build
       [not found] ` <e2efea97-9cdb-4dac-bf9b-324e77a2817f@redhat.com>
@ 2025-08-18  7:02   ` Stefan Weil via
  2025-08-18  7:08     ` Thomas Huth
  0 siblings, 1 reply; 4+ messages in thread
From: Stefan Weil via @ 2025-08-18  7:02 UTC (permalink / raw)
  To: Thomas Huth; +Cc: qemu-devel

Am 18.08.25 um 07:49 schrieb Thomas Huth:
> I'll queue your patch for my next pull request ... just wondering: Did 
> you run into any real issue here? AFAIK we're not running any related 
> test on Windows in the CI, so there should not be any big difference?

Hi,

HTTPS connections don't work unless the server certificate can be 
validated. Binaries with mingw-w64-x86_64-curl won't find the common CA 
certificates, so server certificates cannot be validated and HTTPS 
connections fail. With mingw-w64-x86_64-curl-winssl, the installed CA 
certificates from Windows are used and HTTPS works fine.

The difference is therefore for any protocol which uses SSL. I assume 
that there is no difference for other protocols which are supported by 
curl, but did not test this.

Stefan



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH for-10.1] CI: Use mingw-w64-x86_64-curl-winssl instead of mingw-w64-x86_64-curl for Windows build
  2025-08-18  7:02   ` [PATCH for-10.1] CI: Use mingw-w64-x86_64-curl-winssl instead of mingw-w64-x86_64-curl for Windows build Stefan Weil via
@ 2025-08-18  7:08     ` Thomas Huth
  0 siblings, 0 replies; 4+ messages in thread
From: Thomas Huth @ 2025-08-18  7:08 UTC (permalink / raw)
  To: Stefan Weil; +Cc: qemu-devel

On 18/08/2025 09.02, Stefan Weil wrote:
> Am 18.08.25 um 07:49 schrieb Thomas Huth:
>> I'll queue your patch for my next pull request ... just wondering: Did you 
>> run into any real issue here? AFAIK we're not running any related test on 
>> Windows in the CI, so there should not be any big difference?
> 
> Hi,
> 
> HTTPS connections don't work unless the server certificate can be validated. 
> Binaries with mingw-w64-x86_64-curl won't find the common CA certificates, 
> so server certificates cannot be validated and HTTPS connections fail. 
> With mingw-w64-x86_64-curl-winssl, the installed CA certificates from 
> Windows are used and HTTPS works fine.
> 
> The difference is therefore for any protocol which uses SSL.

Sure, but I was just wondering whether you observed a failure in a CI job. 
AFAIK we don't run any QEMU binary in that CI job, so the CI job itself 
should not hit the problem. And we don't publish the binaries as artifacts 
of the job either, so there's also no user that could run into this problem 
with the generated binaries there.

But anyway, it's better to fix it, in case someone uses the list in the yml 
file for their local installation to build QEMU, or in case we ever decide 
to publish the binaries from the CI job for consumption by the users.

  Thomas



^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2025-08-18  7:09 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <c4bcc116-bd15-4c86-9e7b-3bf33b31e792@weilnetz.de>
     [not found] ` <e2efea97-9cdb-4dac-bf9b-324e77a2817f@redhat.com>
2025-08-18  7:02   ` [PATCH for-10.1] CI: Use mingw-w64-x86_64-curl-winssl instead of mingw-w64-x86_64-curl for Windows build Stefan Weil via
2025-08-18  7:08     ` Thomas Huth
2025-08-06 20:09 Stefan Weil via
2025-08-06 20:27 ` Pierrick Bouvier

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).