From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35648) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f4RUm-0008CY-Tu for qemu-devel@nongnu.org; Fri, 06 Apr 2018 09:33:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f4RUl-0004aV-Tl for qemu-devel@nongnu.org; Fri, 06 Apr 2018 09:33:36 -0400 Received: from mail-ot0-x244.google.com ([2607:f8b0:4003:c0f::244]:45923) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1f4RUl-0004aG-OL for qemu-devel@nongnu.org; Fri, 06 Apr 2018 09:33:35 -0400 Received: by mail-ot0-x244.google.com with SMTP id h26-v6so1158437otj.12 for ; Fri, 06 Apr 2018 06:33:35 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: Peter Maydell Date: Fri, 6 Apr 2018 14:33:14 +0100 Message-ID: Content-Type: text/plain; charset="UTF-8" Subject: Re: [Qemu-devel] -icount changes physical address assignments in QEMU 2.10/2.11 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: alarson@ddci.com Cc: QEMU Developers , Stefan Weil On 6 April 2018 at 14:28, wrote: > "Peter Maydell" wrote: >> On 5 April 2018 at 22:23, 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