On 6 April 2018 at 14:28, <alar...@ddci.com> wrote: > "Peter Maydell" <peter.mayd...@linaro.org> wrote: >> On 5 April 2018 at 22:23, <alar...@ddci.com> wrote: >> > I installed a fresh Cygwin with just the packages suggested at >> > https://wiki.qemu.org/Hosts/W32#Native_builds_with_Mingw-w64 (plus >> > some obviously missing ones like python, make, etc.) and the problem >> > persists. The updated configure line is: >> > >> > ../qemu-2.12.0-rc2/configure \ >> > '--with-pkgversion=DDCI QEMU 2.12.0-rc2' \ >> > --prefix=/usr/local/qemu \ >> > '--target-list=aarch64-softmmu ppc64-softmmu x86_64-softmmu' \ >> > --cross-prefix=i686-w64-mingw32- >> >> Hmm, if it's Windows-only that's unfortunate, since I'm not really >> in a position to debug things that only happon on Windows hosts. >> >> Stefan, does this sort of bug sound familiar at all? >> >> Looking at your --cross-prefix you seem to be building 32-bit >> binaries; was your Ubuntu VM 32 bit or 64 bit? I'm wondering >> if this might turn out to be a 32-bit host issue rather than >> necessarily a Windows one. > > 1. Ubuntu 17.10 is 64-bit, compilation was native, run on the > compilation host. I.e., I did not cross compile to windows. > 2. Cygwin was a 64-bit install, 64-bit windows 7 host. I followed the > instructions on the wiki. I was curious about the "ming32" part > myself, but cygwin package search doesn't indicate an obvious (to > me) replacement.
You're building your mingw32 binaries with an i686- compiler, not an x86_64- one, so you'll end up with 32-bit Windows binaries running on your 64-bit Windows installation. If you have the 64-bit cross compiler and libraries for it you could try a --cross-prefix=x86_64-w64-mingw32- build. On this end I should try this with a 32-bit Linux host. thanks -- PMM
