qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil via <qemu-devel@nongnu.org>
To: BALATON Zoltan <balaton@eik.bme.hu>,
	Howard Spoelstra <hsp.cat7@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: source fails to compile on msys2
Date: Wed, 12 Apr 2023 14:28:31 +0200	[thread overview]
Message-ID: <ec51176a-1b2f-c8bd-49d5-e41734e4aedd@weilnetz.de> (raw)
In-Reply-To: <1aacbfc4-2303-4d9c-7644-32ad97d6d748@eik.bme.hu>

Am 12.04.23 um 14:12 schrieb BALATON Zoltan:

> On Wed, 12 Apr 2023, Howard Spoelstra wrote:
>> It seems the current source fails to compile with up to date msys2.
>
> See here: https://qemu.weilnetz.de/
> I think there are some patches there that aren't upstream. I don't 
> know why and also don't know why those binaries are not built from 
> QEMU master.


My related Git repository is https://repo.or.cz/w/qemu/ar7.git/. I 
merged v8.0.0-rc3 two days ago, and that code builds with no problems 
for Windows.

And yes, my code includes commits which are (still) missing upstream. 
Some of them are for special hardware which was either removed from QEMU 
master or which I think is not interesting for upstream. Others were 
already sent to qemu-devel, so might become part of QEMU master later. 
In addition there are commits for my Windows build environment which 
also uses a higher warning level than QEMU master. But usually the 
differences to the latest tagged QEMU release are small.

Stefan




  reply	other threads:[~2023-04-12 12:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 12:05 source fails to compile on msys2 Howard Spoelstra
2023-04-12 12:12 ` BALATON Zoltan
2023-04-12 12:28   ` Stefan Weil via [this message]
2023-04-12 12:13 ` Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2023-04-12 13:13 Howard Spoelstra
2023-04-12 13:20 ` Stefan Weil via
2023-04-12 13:38   ` Peter Maydell
2023-04-12 13:39 ` Thomas Huth
2023-04-12 14:29 Howard Spoelstra

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=ec51176a-1b2f-c8bd-49d5-e41734e4aedd@weilnetz.de \
    --to=qemu-devel@nongnu.org \
    --cc=balaton@eik.bme.hu \
    --cc=hsp.cat7@gmail.com \
    --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).