qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PULL 00/11] Disassembler patches


From: Richard Henderson
Subject: Re: [Qemu-devel] [PULL 00/11] Disassembler patches
Date: Thu, 26 Oct 2017 12:04:10 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0

On 10/26/2017 09:21 AM, Peter Maydell wrote:
> On 26 October 2017 at 08:06, Daniel P. Berrange <address@hidden> wrote:
>> I'm not sure what's giving you the 'pathspec' message though ? I would
>> expect anything to ignore the capstone dir - its just like any other
>> untracked file once you go back in time before it was committed.
> 
> Sorry, just realized that was the output of my filtering of the
> log. Here's what I should have quoted:
> 
> From git://git.linaro.org/people/pmaydell/qemu-arm
>  + a872ea5...6315472 staging    -> pmaydell/staging  (forced update)
> warning: unable to rmdir capstone: Directory not empty
> error: pathspec 'capstone' did not match any file(s) known to git.
> Did you forget to 'git add'?
> make: Entering directory `/home/pm215/qemu/build/all'
> config-host.mak is out-of-date, running configure
>   GIT     ui/keycodemapdb dtc capstone
> make[1]: *** No rule to make target `all'.  Stop.
> error: pathspec 'capstone' did not match any file(s) known to git.
> Did you forget to 'git add'?
> make: *** [git-submodule-update] Error 1
> make: *** Waiting for unfinished jobs....
> make: *** [subdir-capstone] Error 2

Looks like we need to make git-submodule-update depend on config-host.mak, so
that we have already re-run configure, so that vanishing modules will have been
de-selected.

Forcing a configure re-run by hand would have masked this problem.  I think all
of the testing that I have been doing has been builds from empty build 
directories.


r~



reply via email to

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