From: Eric Blake <eblake@redhat.com>
To: Roman Kagan <rkagan@virtuozzo.com>,
Viktor Prutyanov <viktor.prutyanov@phystech.edu>,
pbonzini@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] contrib/elf2dmp: elf2dmp for Windows hosts
Date: Wed, 21 Nov 2018 10:54:15 -0600 [thread overview]
Message-ID: <e070434f-939b-fe09-603c-4884ddb849b0@redhat.com> (raw)
In-Reply-To: <20181121102530.GB870@rkaganb.sw.ru>
On 11/21/18 4:25 AM, Roman Kagan wrote:
> On Fri, Nov 02, 2018 at 03:28:18AM +0300, Viktor Prutyanov wrote:
>> After this patch elf2dmp can be built by mingw64 for Windows hosts.
>
> What prevents building it with mingw32? (I realize that since the tool
> uses mmaped access to the dump data it's limited to dumps under a couple
> of gigs but it's still not totally useless).
Careful. The original (32-bit) mingw project is obsolete, and its
replacement, the mingw64 project, provides both 32- and 64-bit
environments. Even more confusingly, Fedora ships the mingw64
cross-compilers under the names i686-w64-mingw32-gcc (build for a 32-bit
environment) and x86_64-w64-mingw32-gcc (build for a 64-bit
environment). Historical naming causes confusion.
So your question may not be relevant, especially given that
tests/docker/test-mingw builds both 32- and 64-bit mingw builds.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-11-21 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 0:28 [Qemu-devel] [PATCH 0/2] contrib/elf2dmp: elf2dmp for Windows hosts Viktor Prutyanov
2018-11-02 0:28 ` [Qemu-devel] [PATCH 1/2] contrib/elf2dmp: use GLib file mapping Viktor Prutyanov
2018-11-05 22:58 ` Eric Blake
2018-11-21 10:08 ` Roman Kagan
2018-11-02 0:28 ` [Qemu-devel] [PATCH 2/2] contrib/elf2dmp: elf2dmp for Windows hosts Viktor Prutyanov
2018-11-21 10:25 ` Roman Kagan
2018-11-21 16:54 ` Eric Blake [this message]
2018-11-22 9:04 ` Roman Kagan
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=e070434f-939b-fe09-603c-4884ddb849b0@redhat.com \
--to=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkagan@virtuozzo.com \
--cc=viktor.prutyanov@phystech.edu \
/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).