From: Helge Konetzka <hk@zapateado.de>
To: Howard Spoelstra <hsp.cat7@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [qemu-web PATCH] Fix link to Windows page in Wiki
Date: Sat, 11 Sep 2021 11:29:52 +0200 [thread overview]
Message-ID: <b353ed86-43e8-498d-1d92-a5d0434da93d@zapateado.de> (raw)
In-Reply-To: <CABLmASEuNT2WVocMwakuhhYDvVBB0YdFueP24ULRFQ1Z35eKPg@mail.gmail.com>
Am 11.09.21 um 10:43 schrieb Howard Spoelstra:
>
> Perhaps it would be better to fix configure for the MSYS2 case so the
> flags or the renaming are not required?
>
Currently MSys2 packages qemu successfully for 3 different toolchains:
MINGW64: msvcrt / libstdc++
UCRT64: ucrt / libstdc++
CLANG64: ucrt libc++
see https://www.msys2.org/docs/environments/ and
https://packages.msys2.org/base/mingw-w64-qemu
For CLANG64 configure needs different flags - all other flag-definitions
failed:
AR=llvm-ar RANLIB=llvm-ranlib NM=nm OBJCOPY=objcopy STRIP=strip
WINDRES=windres \
./configure.sh --cross-prefix=x86_64-w64-mingw32- --enable-gtk --enable-sdl
see
https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-qemu/PKGBUILD
Just a note to keep in mind if someone wants to fix.
Regards Helge.
prev parent reply other threads:[~2021-09-11 9:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 16:43 [qemu-web PATCH] Fix link to Windows page in Wiki Helge Konetzka
2021-09-01 15:30 ` Stefano Garzarella
2021-09-10 15:44 ` Paolo Bonzini
2021-09-11 6:28 ` Helge Konetzka
2021-09-11 8:43 ` Howard Spoelstra
2021-09-11 9:03 ` Mark Cave-Ayland
2021-09-11 9:17 ` Mark Cave-Ayland
2021-09-11 9:17 ` Helge Konetzka
2021-09-11 9:30 ` Mark Cave-Ayland
2021-09-12 8:15 ` Helge Konetzka
2021-09-11 9:09 ` Paolo Bonzini
2021-09-11 9:29 ` Helge Konetzka [this message]
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=b353ed86-43e8-498d-1d92-a5d0434da93d@zapateado.de \
--to=hk@zapateado.de \
--cc=hsp.cat7@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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).