qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] -icount changes physical address assignments in QEMU 2.


From: alarson
Subject: Re: [Qemu-devel] -icount changes physical address assignments in QEMU 2.10/2.11
Date: Fri, 6 Apr 2018 15:15:12 -0500

"Mark Cave-Ayland" <address@hidden> wrote on 04/06/2018 
09:14:14 AM:

> From: "Mark Cave-Ayland" <address@hidden>
> To: address@hidden, "Peter Maydell" <address@hidden>
> Cc: "Stefan Weil" <address@hidden>, "QEMU Developers" 
<address@hidden>
> Date: 04/06/2018 09:14 AM
> Subject: Re: [Qemu-devel] -icount changes physical address assignments 
in QEMU 2.10/2.11
> 
> On 06/04/18 14:28, address@hidden wrote:
> 
> > I was not successful with the wiki instructions for "Native builds
> > with MSYS2":
> > 
> >    ./qemu-2.12.0-rc2/configure --python=/usr/bin/python2 \
> >        '--with-pkgversion=DDCI QEMU 2.12.0-rc2' \
> >        --prefix=/usr/local/qemu \
> >        '--target-list=aarch64-softmmu ppc64-softmmu x86_64-softmmu'
> >    make
> >    ...
> >    C:\msys2-x86_64_20161025\msys64\mingw64\bin\ar.exe: creating
> > libfdt/libfdt.a
> >    make[1]: *** No rule to make target 
...build/capstone/capstone.lib'.
> > Stop.
> >    make: *** [Makefile:503: subdir-capstone] Error 2
> 
> Ah I believe those instructions were mine from when I had temporary 
> access to a Windows VM for testing last year.
> 
> Since the instructions pre-dated the inclusion of capstone as a 
> dependency, is it as simple as adding:
> 
> git submodule update --init capstone
> 
> before running configure and make?

I didn't do the "git" parts.  I extracted from the source tarball.
Is the tarball source supposed to work, or is it necessary to always
use git?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]