On Thu, Oct 26, 2017 at 07:16:45AM +0100, Peter Maydell wrote: > On 26 October 2017 at 07:07, Peter Maydell <peter.mayd...@linaro.org> wrote: > > Hi. This failed to build for Windows: > > Also, after it failed and I backed out the merge, the next thing I > tried to build failed everywhere with: > > warning: unable to rmdir capstone: Directory not empty > error: pathspec 'capstone' did not match any file(s) known to git. > error: pathspec 'capstone' did not match any file(s) known to git. > > That's bad, because it suggests that bisection is going to break > across this merge commit. > > Dan, is this going to be a generic problem with the new submodule > stuff, or is it specific to something with how the capstone > submodule is being handled in this patchset?
If you make your checkout go back in time to before the submodule existed, git won't delete your checked out submodule - in case you have commits there you still care about. So it'll print that warning about unable to 'rmdir'. This should be harmless to the build process in general though. 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. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
