qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Konstantin Kostiuk <kkostiuk@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Stefan Weil" <sw@weilnetz.de>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	QEMU <qemu-devel@nongnu.org>,
	"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [PULL 2/3] qga-win32: Add support for NVME but type
Date: Tue, 24 May 2022 15:13:17 +0200	[thread overview]
Message-ID: <449f117b-32c9-e066-55dd-1208313bce3f@redhat.com> (raw)
In-Reply-To: <CAPMcbCr8_zgYcMQ9Q0GSQL-TgvOGY-q16sMoVNxBpvwG4JDEng@mail.gmail.com>

On 24/05/2022 15.00, Konstantin Kostiuk wrote:
> 
> 
> 
> 
> On Tue, May 24, 2022 at 1:24 PM Thomas Huth <thuth@redhat.com 
> <mailto:thuth@redhat.com>> wrote:
> 
>     On 24/05/2022 12.14, Marc-André Lureau wrote:
>      > Hi
>      >
>      > On Tue, May 24, 2022 at 12:02 PM Konstantin Kostiuk
>     <kkostiuk@redhat.com <mailto:kkostiuk@redhat.com>> wrote:
>      >>
>      >> Hi Richard and Marc-André
>      >>
>      >> I looked into the compilation problem and have 2 solutions:
>      >> 1. We can add some conditions to the win2qemu definition and
>      >> skip NVME support when old mingw-headers are used.
>      >> 2. We can bump the version of the Fedora docker image to 36 or 37
>      >> that is used for cross-compilation tests.
>      >>
>      >> I think the second option is more valuable because we remove
>      >> pregenerated qga-vss.tlb file and now we can check VSS build only
>      >> at Fedora 37.
>      >>
>      >> What do you think?
>      >
>      > I'd try to do both: fix compilation with older headers, and bump our
>      > CI to f36. I don't know if our windows build environment has strict
>      > requirements like the unix/distro (build on old-stable for 2y).
> 
>     See https://www.qemu.org/docs/master/about/build-platforms.html#windows
>     <https://www.qemu.org/docs/master/about/build-platforms.html#windows> :
> 
>     "The project supports building QEMU with current versions of the MinGW
>     toolchain, either hosted on Linux (Debian/Fedora) or via MSYS2 on Windows."
> 
>     Since Fedora 35 is still a supported build host, I think you should make
>     sure that it works with the MinGW toolchain from that distro, too.
> 
> 
> Currently, CI uses Fedora 33 which is already EOL. Fedora 35 has updated
> mingw-headers and the current version of code compiles without any errors.
> So if we want to support only Fedora 35+, we can just bump the CI docker image.

Ah, right, I was looking at the wrong file. So yes, in that case, please 
simply update the docker image.

What about Debian (since this is mentioned on the support page, too)? I 
think we don't have to worry about Debian 10 anymore, since Debian 10 will 
already be EOL once we release QEMU 7.1 ... but what about Debian 11? Do the 
MinGW packages there contain the updated headers, too?

  Thomas



  reply	other threads:[~2022-05-24 13:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 19:41 [PULL 0/3] qemu-ga patches Konstantin Kostiuk
2022-05-23 19:41 ` [PULL 1/3] qga: add guest-get-diskstats command for Linux guests Konstantin Kostiuk
2022-05-23 19:41 ` [PULL 2/3] qga-win32: Add support for NVME but type Konstantin Kostiuk
2022-05-23 20:55   ` Richard Henderson
2022-05-24  9:26     ` Konstantin Kostiuk
2022-05-24 10:01       ` Konstantin Kostiuk
2022-05-24 10:14         ` Marc-André Lureau
2022-05-24 10:24           ` Thomas Huth
2022-05-24 13:00             ` Konstantin Kostiuk
2022-05-24 13:13               ` Thomas Huth [this message]
2022-05-24 13:17                 ` Konstantin Kostiuk
2022-05-24 13:28                   ` Thomas Huth
2022-05-24 13:33                     ` Thomas Huth
2022-05-24 13:38                     ` Daniel P. Berrangé
2022-06-03 12:56                       ` Debian MinGW cross compilation (was: Re: [PULL 2/3] qga-win32: Add support for NVME but type) Thomas Huth
2022-06-03 13:09                         ` Stefan Weil via
2022-06-03 13:15                           ` Thomas Huth
2022-05-24 10:16       ` [PULL 2/3] qga-win32: Add support for NVME but type Peter Maydell
2022-05-23 19:41 ` [PULL 3/3] trivial: qga: Log version on start Konstantin Kostiuk

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=449f117b-32c9-e066-55dd-1208313bce3f@redhat.com \
    --to=thuth@redhat.com \
    --cc=kkostiuk@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=sw@weilnetz.de \
    /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).