From: Helge Konetzka <hk@zapateado.de>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
Howard Spoelstra <hsp.cat7@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
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:17:46 +0200 [thread overview]
Message-ID: <43043204-cb7a-5726-ecfc-9dad504f6aa3@zapateado.de> (raw)
In-Reply-To: <6ae0c8d0-4601-4c2c-c0cd-590f2a86a104@ilande.co.uk>
Am 11.09.21 um 11:03 schrieb Mark Cave-Ayland:
> So the question is: what has changed? I find it hard to believe that
> MSYS2/MingW64 is configured out-of-the-box to break a standard
> "./configure && make" build incantation.
>
On my last attempt to build qemu without
--cross-prefix=x86_64-w64-mingw32- (qemu-6.1.0.tar.xz) for building
target soft-mmu-x86_64 I received
make[1]: *** No rule to make target 'multiboot.bin', needed by 'all'. Stop.
make: *** [Makefile:189: pc-bios/optionrom/all] Error 2
make: *** Waiting for unfinished jobs....
...
[1599/1599] Generating QAPI rST doc reference newline-sanitized with a
custom command (wrapped by meson to capture output)
==> ERROR: A failure occurred in build().
Aborting...
next prev parent reply other threads:[~2021-09-11 9:19 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 [this message]
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
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=43043204-cb7a-5726-ecfc-9dad504f6aa3@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).