configure: Change capstone's default state to disabled
PATCH 1/1 configure: Change capstone's default state to disabled
Capstone is not necessary in order to use QEMU. Disable it by default. This will save the user the pain of having to figure why QEMU isn't building when this library is missing.
--- configure | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
configure +1 -1
@@ -433,7 +433,7 @@ opengl_dmabuf="no" cpuid_h="no" avx2_opt="" zlib="yes" -capstone="" +capstone="no" lzo="" snappy="" bzip2=""
Signature · 1 line
2.14.3 (Apple Git-98)
Quoted 14 lines · John Arbuckle
Capstone is not necessary in order to use QEMU. Disable it by default. This will save the user the pain of having to figure why QEMU isn't building when this library is missing.
Signed-off-by John Arbuckle <[email protected]>--- configure | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)configure +0
-0
configure opengl_dmabuf="no" · line 439
Quoted 8 lines
configure +1
-1@@ -433,7 +433,7 @@ opengl_dmabuf="no" cpuid_h="no" avx2_opt="" zlib="yes" -capstone="" +capstone="no" lzo="" snappy="" bzip2=""
AFAIK we ship capstone as a submodule, so how can this be missing? Also, our philosophy is to keep everything enabled by default if possible, so that the code paths don't bitrot. Thus I don't think that disabling this by default is a good idea. ... so if you've got a problem here, there must be another solution (e.g. is the system capstone detection not working right on your system?).
Thomas
Quoted 31 lines · Thomas Huth
Quoted 14 lines · John Arbuckle
Capstone is not necessary in order to use QEMU. Disable it by default. This will save the user the pain of having to figure why QEMU isn't building when this library is missing.
Signed-off-by John Arbuckle <[email protected]>--- configure | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)configure +0
-0configure opengl_dmabuf="no" · line 439
Quoted 8 lines
configure +1
-1@@ -433,7 +433,7 @@ opengl_dmabuf="no" cpuid_h="no" avx2_opt="" zlib="yes" -capstone="" +capstone="no" lzo="" snappy="" bzip2=""AFAIK we ship capstone as a submodule, so how can this be missing? Also, our philosophy is to keep everything enabled by default if possible, so that the code paths don't bitrot. Thus I don't think that disabling this by default is a good idea. ... so if you've got a problem here, there must be another solution (e.g. is the system capstone detection not working right on your system?).
Quoted 1 line
Thomas
Thank you for replying. Capstone comes with QEMU? Every time I try to compile QEMU I see an error relating to Capstone not being on my system. Why do you feel that disabling Capstone by default is not a good idea?
Here is the error message I see when compiling QEMU:
CHK version_gen.h
make[1]: *** No rule to make target `/Users/John/qemu-git/capstone/libcapstone.a'. Stop.
make: *** [subdir-capstone] Error 2
Quoted 7 lines · On 4/19/19 3:44 AM, G 3 wrote:
Here is the error message I see when compiling QEMU:
CHK
version_gen.h
make[1]: *** No rule to make target `/Users/John/qemu-git/capstone/libcapstone.a'. Stop.
make: *** [subdir-capstone] Error 2
You are configuring with --static?
I've seen this before myself -- IMO it's broken distro packaging, in that the shipped pkgconfig/capstone.pc claims static library support, but the static library itself wasn't shipped.
We should probably work around this in configure, and report the packaging bug.
r~
Quoted 12 lines · Richard Henderson
Quoted 7 lines · On 4/19/19 3:44 AM, G 3 wrote:
Here is the error message I see when compiling QEMU:
CHK
version_gen.h
make[1]: *** No rule to make target `/Users/John/qemu-git/capstone/libcapstone.a'. Stop.
make: *** [subdir-capstone] Error 2
Quoted 7 lines
You are configuring with --static?
I've seen this before myself -- IMO it's broken distro packaging, in that the shipped pkgconfig/capstone.pc claims static library support, but the static library itself wasn't shipped.
We should probably work around this in configure, and report the packaging bug.
I do not use --static. This is what I use: ./configure --target-list=ppc-softmmu.
I think this is a bug with configure, or with the capstone repo.
Quoted 40 lines · On 19/04/2019 15.44, G 3 wrote:
Quoted 31 lines · Thomas Huth
Quoted 19 lines · John Arbuckle
Capstone is not necessary in order to use QEMU. Disable it by default. This will save the user the pain of having to figure why QEMU isn't building when this library is missing.
Signed-off-by John Arbuckle <[email protected]>---
configure | 2 +-1 file changed, 1 insertion(+), 1 deletion(-)configure +0
-0@@ -433,7 +433,7 @@ opengl_dmabuf="no"cpuid_h="no"
avx2_opt=""
zlib="yes"configure +1
-1-capstone="" +capstone="no"Quoted 3 lines
lzo=""
snappy=""
bzip2=""AFAIK we ship capstone as a submodule, so how can this be missing? Also, our philosophy is to keep everything enabled by default if possible, so that the code paths don't bitrot. Thus I don't think that disabling this by default is a good idea. ... so if you've got a problem here, there must be another solution (e.g. is the system capstone detection not working right on your system?).
Quoted 1 line
Thomas
Thank you for replying. Capstone comes with QEMU? Every time I try to compile QEMU I see an error relating to Capstone not being on my system. Why do you feel that disabling Capstone by default is not a good idea?
Quoted 6 lines
Here is the error message I see when compiling QEMU:
CHK
version_gen.h
make[1]: *** No rule to make target `/Users/John/qemu-git/capstone/libcapstone.a'. Stop.
make: *** [subdir-capstone] Error 2
I assume you're using a git checkout here, right? For git checkouts, the Makefile should take care of calling the scripts/git-submodule.sh script which should initialize the submodule in the capstone directory.
What's the content of your .git-submodule-status file? What does "configure" say about capstone support on your system?
Thomas
Quoted 51 lines · Thomas Huth
Quoted 40 lines · On 19/04/2019 15.44, G 3 wrote:
Quoted 31 lines · Thomas Huth
Quoted 14 lines · John Arbuckle
Capstone is not necessary in order to use QEMU. Disable it by default. This will save the user the pain of having to figure why QEMU isn't building when this library is missing.
Signed-off-by John Arbuckle <[email protected]>--- configure | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)configure +0
-0configure opengl_dmabuf="no" · line 439
Quoted 8 lines
configure +1
-1@@ -433,7 +433,7 @@ opengl_dmabuf="no" cpuid_h="no" avx2_opt="" zlib="yes" -capstone="" +capstone="no" lzo="" snappy="" bzip2=""AFAIK we ship capstone as a submodule, so how can this be missing? Also, our philosophy is to keep everything enabled by default if possible, so that the code paths don't bitrot. Thus I don't think that disabling this by default is a good idea. ... so if you've got a problem here, there must be another solution (e.g. is the system capstone detection not working right on your system?).
Quoted 1 line
Thomas
Thank you for replying. Capstone comes with QEMU? Every time I try to compile QEMU I see an error relating to Capstone not being on my system. Why do you feel that disabling Capstone by default is not a good idea?
Quoted 6 lines
Here is the error message I see when compiling QEMU:
CHK
version_gen.h
make[1]: *** No rule to make target `/Users/John/qemu-git/capstone/libcapstone.a'. Stop.
make: *** [subdir-capstone] Error 2
Quoted 8 lines
I assume you're using a git checkout here, right? For git checkouts, the
Makefileshould take care of calling thescripts/git-submodule.shscript which should initialize the submodule in the capstone directory.What's the content of your .git-submodule-status file? What does "configure" say about capstone support on your system?
Thomas
Yes I use a git checkout.
This is the contents of my .git-submodule-status file:
#!/bin/sh
#
# This code is licensed under the GPL version 2 or later. See
# the COPYING file in the top-level directory.
substat=".git-submodule-status"
command=$1
shift
maybe_modules="$@"
test -z "$GIT" && GIT=git
error() {
echo "$0: $*"
echo
echo "Unable to automatically checkout GIT submodules '$modules'." echo "If you require use of an alternative GIT binary (for example to" echo "enable use of a transparent proxy), then please specify it by" echo "running configure by with the '--with-git' argument. e.g." echo
echo " $ ./configure --with-git='tsocks git'"
echo
echo "Alternatively you may disable automatic GIT submodule checkout" echo "with:"
echo
echo " $ ./configure --disable-git-update"
echo
echo "and then manually update submodules prior to running make, with:" echo
echo " $ scripts/git-submodule.sh update $modules"
echo
exit 1
}
modules=""
for m in $maybe_modules
do
$GIT submodule status $m 1> /dev/null 2>&1 if test $? = 0
then
modules="$modules $m"
else
echo "warn: ignoring non-existent submodule $m"
fi
done
if test -n "$maybe_modules" && ! test -e ".git"
then
echo "$0: unexpectedly called with submodules but no git checkout exists" exit 1
fi
case "$command" in
status)
if test -z "$maybe_modules"
then
test -s ${substat} && exit 1 || exit 0
fi
test -f "$substat" || exit 1
CURSTATUS=$($GIT submodule status $modules)
OLDSTATUS=$(cat $substat)
test "$CURSTATUS" = "$OLDSTATUS"
exit $?
;;
update)
if test -z "$maybe_modules"
then
test -e $substat || touch $substat
exit 0
fi
$GIT submodule update --init $modules 1>/dev/null
test $? -ne 0 && error "failed to update modules"
$GIT submodule status $modules > "${substat}"
test $? -ne 0 && error "failed to save git submodule status" >&2
;;esac
exit 0
The Configure command says:
capstone git
I did a 'make clean' followed by a 'make distclean'. Then tried building again using this command line:
./configure --target-list=ppc-softmmu,i386-softmmu,x86_64-softmmu make -j 4
Here is the error message I see:
make[1]: *** No rule to make target `/Users/John/Documents/Development/Projects/Qemu/qemu-git/capstone/libcapstone.a'. Stop.
make: *** [subdir-capstone] Error 2
I took a look at the capstone folder. There is no 'make' file in this folder. Should there be one?
Thank you.
Quoted 58 lines · Programmingkid
Quoted 58 lines · Thomas Huth
Quoted 40 lines · On 19/04/2019 15.44, G 3 wrote:
Quoted 31 lines · Thomas Huth
Quoted 14 lines · John Arbuckle
Capstone is not necessary in order to use QEMU. Disable it by default. This will save the user the pain of having to figure why QEMU isn't building when this library is missing.
Signed-off-by John Arbuckle <[email protected]>--- configure | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)configure +0
-0configure opengl_dmabuf="no" · line 439
Quoted 8 lines
configure +1
-1@@ -433,7 +433,7 @@ opengl_dmabuf="no" cpuid_h="no" avx2_opt="" zlib="yes" -capstone="" +capstone="no" lzo="" snappy="" bzip2=""AFAIK we ship capstone as a submodule, so how can this be missing? Also, our philosophy is to keep everything enabled by default if possible, so that the code paths don't bitrot. Thus I don't think that disabling this by default is a good idea. ... so if you've got a problem here, there must be another solution (e.g. is the system capstone detection not working right on your system?).
Quoted 1 line
Thomas
Thank you for replying. Capstone comes with QEMU? Every time I try to compile QEMU I see an error relating to Capstone not being on my system. Why do you feel that disabling Capstone by default is not a good idea?
Quoted 6 lines
Here is the error message I see when compiling QEMU:
CHK
version_gen.h
make[1]: *** No rule to make target `/Users/John/qemu-git/capstone/libcapstone.a'. Stop.
make: *** [subdir-capstone] Error 2I assume you're using a git checkout here, right? For git checkouts, the
Makefileshould take care of calling thescripts/git-submodule.shscript which should initialize the submodule in the capstone directory.What's the content of your .git-submodule-status file? What does "configure" say about capstone support on your system?
Quoted 6 lines
Quoted 1 line
Thomas
Yes I use a git checkout.
This is the contents of my .git-submodule-status file:
#!/bin/sh
[...]
That were the contents of scripts/git-submodule.sh. I meant the hidden file .git-submodule-status in the main directory.
Quoted 4 lines
I did a 'make clean' followed by a 'make distclean'. Then tried building again using this command line:
./configure --target-list=ppc-softmmu,i386-softmmu,x86_64-softmmu make -j 4
That should normally populate the capstone directory. What happens if you run "make git-submodule-update" directly?
Quoted 6 lines
Here is the error message I see:
make[1]: *** No rule to make target `/Users/John/Documents/Development/Projects/Qemu/qemu-git/capstone/libcapstone.a'. Stop.
make: *** [subdir-capstone] Error 2I took a look at the capstone folder. There is no 'make' file in this folder. Should there be one?
Yes, the capstone folder should be populated automatically. Is it completely empty for you?
Thomas
Quoted 64 lines · Thomas Huth
Quoted 60 lines · Programmingkid
Quoted 59 lines · Thomas Huth
Quoted 40 lines · On 19/04/2019 15.44, G 3 wrote:
Quoted 31 lines · Thomas Huth
Quoted 19 lines · John Arbuckle
Capstone is not necessary in order to use QEMU. Disable it by default. This will save the user the pain of having to figure why QEMU isn't building when this library is missing.
Signed-off-by John Arbuckle <[email protected]>---
configure | 2 +-1 file changed, 1 insertion(+), 1 deletion(-)configure +0
-0@@ -433,7 +433,7 @@ opengl_dmabuf="no"cpuid_h="no"
avx2_opt=""
zlib="yes"configure +1
-1-capstone="" +capstone="no"Quoted 3 lines
lzo=""
snappy=""
bzip2=""AFAIK we ship capstone as a submodule, so how can this be missing? Also, our philosophy is to keep everything enabled by default if possible, so that the code paths don't bitrot. Thus I don't think that disabling this by default is a good idea. ... so if you've got a problem here, there must be another solution (e.g. is the system capstone detection not working right on your system?).
Quoted 1 line
Thomas
Thank you for replying. Capstone comes with QEMU? Every time I try to compile QEMU I see an error relating to Capstone not being on my system. Why do you feel that disabling Capstone by default is not a good idea?
Quoted 6 lines
Here is the error message I see when compiling QEMU:
CHK
version_gen.h
make[1]: *** No rule to make target `/Users/John/qemu-git/capstone/libcapstone.a'. Stop.
make: *** [subdir-capstone] Error 2I assume you're using a git checkout here, right? For git checkouts, the
Makefileshould take care of calling thescripts/git-submodule.shscript which should initialize the submodule in the capstone directory.What's the content of your .git-submodule-status file? What does "configure" say about capstone support on your system?
Thomas
Quoted 8 lines
Quoted 4 lines
Yes I use a git checkout.
This is the contents of my .git-submodule-status file:
#!/bin/sh[...]
That were the contents of
scripts/git-submodule.sh. I meant the hidden file .git-submodule-status in the main directory.
This is it:
88f18909db731a627456f26d779445f84e449536 dtc (v1.4.7) f0da6726207b740f6101028b2992f918477a4b08 slirp (v4.0.0-rc0-25-gf0da672) b64af41c3276f97f0e181920400ee056b9c88037 tests/fp/berkeley-softfloat-3 (heads/master) 5a59dcec19327396a011a17fd924aed4fec416b3 tests/fp/berkeley-testfloat-3 (remotes/origin/HEAD) 6b3d716e2b6472eb7189d3220552280ef3d832ce ui/keycodemapdb (heads/master-4-g6b3d716)
Quoted 8 lines
Quoted 5 lines
I did a 'make clean' followed by a 'make distclean'. Then tried building again using this command line:
./configure --target-list=ppc-softmmu,i386-softmmu,x86_64-softmmu make -j 4
That should normally populate the capstone directory. What happens if you run "make git-submodule-update" directly?
Here is the result:
$ make git-submodule-update make[1]: Nothing to be done for `all'. make[1]: *** No rule to make target `/Users/John/Documents/Development/Projects/Qemu/qemu-git/capstone/libcapstone.a'. Stop. make: *** [subdir-capstone] Error 2
Quoted 9 lines
Quoted 6 lines
Here is the error message I see:
make[1]: *** No rule to make target `/Users/John/Documents/Development/Projects/Qemu/qemu-git/capstone/libcapstone.a'. Stop.
make: *** [subdir-capstone] Error 2I took a look at the capstone folder. There is no 'make' file in this folder. Should there be one?
Yes, the capstone folder should be populated automatically. Is it completely empty for you?
It isn't empty. All I see are two folders: obj and docs.
Thank you.
Quoted 8 lines · Programmingkid
Quoted 8 lines · Thomas Huth
Quoted 4 lines · Programmingkid
Quoted 4 lines · Thomas Huth
On 19/04/2019 15.44, G 3 wrote:
[...]
Quoted 29 lines
Quoted 20 lines
Quoted 20 lines
Quoted 19 lines
Quoted 10 lines
Thank you for replying. Capstone comes with QEMU? Every time I try to compile QEMU I see an error relating to Capstone not being on my system. Why do you feel that disabling Capstone by default is not a good idea?
Here is the error message I see when compiling QEMU:
CHK
version_gen.h
make[1]: *** No rule to make target `/Users/John/qemu-git/capstone/libcapstone.a'. Stop.
make: *** [subdir-capstone] Error 2I assume you're using a git checkout here, right? For git checkouts, the
Makefileshould take care of calling thescripts/git-submodule.shscript which should initialize the submodule in the capstone directory.What's the content of your .git-submodule-status file? What does "configure" say about capstone support on your system?
Thomas
Quoted 8 lines
Quoted 4 lines
Yes I use a git checkout.
This is the contents of my .git-submodule-status file:
#!/bin/sh[...]
That were the contents of
scripts/git-submodule.sh. I meant the hidden file .git-submodule-status in the main directory.
Quoted 6 lines
This is it:
88f18909db731a627456f26d779445f84e449536dtc (v1.4.7)f0da6726207b740f6101028b2992f918477a4b08slirp (v4.0.0-rc0-25-gf0da672)b64af41c3276f97f0e181920400ee056b9c88037tests/fp/berkeley-softfloat-3 (heads/master)5a59dcec19327396a011a17fd924aed4fec416b3tests/fp/berkeley-testfloat-3 (remotes/origin/HEAD)6b3d716e2b6472eb7189d3220552280ef3d832ceui/keycodemapdb (heads/master-4-g6b3d716)
There should be an entry for capstone in here, too. :-/
Quoted 5 lines
Quoted 5 lines
Quoted 4 lines
I did a 'make clean' followed by a 'make distclean'. Then tried building again using this command line:
./configure --target-list=ppc-softmmu,i386-softmmu,x86_64-softmmu make -j 4
Quoted 8 lines
Quoted 2 lines
That should normally populate the capstone directory. What happens if you run "make git-submodule-update" directly?
Here is the result:
$ make git-submodule-update make[1]: Nothing to be done for `all'. make[1]: *** No rule to make target `/Users/John/Documents/Development/Projects/Qemu/qemu-git/capstone/libcapstone.a'. Stop. make: *** [subdir-capstone] Error 2
Apparently the submodule update is not working right for you. What do you get when you run:
git submodule update capstone
?
Quoted 6 lines
Quoted 4 lines
Quoted 1 line
I took a look at the capstone folder. There is no 'make' file in this folder. Should there be one?
Yes, the capstone folder should be populated automatically. Is it completely empty for you?
It isn't empty. All I see are two folders: obj and docs.
Maybe try to clean the folder first:
rm -r capstone
mkdir capstone
make git-submodule-update
If that does not help, maybe try a completely fresh git checkout?
Thomas
Quoted 7 lines · Thomas Huth
Maybe try to clean the folder first:
rm -r capstone
mkdir capstone
make git-submodule-updateIf that does not help, maybe try a completely fresh git checkout?
Rather than deleting stuff like that, it is best to use git to put your dir back to a clean state.
git submodule deinit --all --force git clean -f -x -d
After doing this, then run 'configure' again with normal args and try to build.
If it still fails, please provide the /full/ output printed by configure, as well as all output from make, and also the contents of the 'config.log' file.
Regards,
Daniel
Signature · 3 lines
|: 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 :|
Quoted 8 lines · Daniel P. Berrangé
Quoted 6 lines · Thomas Huth
Maybe try to clean the folder first:
rm -r capstone
mkdir capstone
make git-submodule-update
Quoted 7 lines
Quoted 1 line
If that does not help, maybe try a completely fresh git checkout?
Rather than deleting stuff like that, it is best to use git to put your dir back to a clean state.
git submodule deinit --all --force git clean -f -x -d
That git clean line will blow away any untracked files in your entire tree, won't it? If so, better move anything you cared about somewhere else first...
thanks
-- PMM
Quoted 14 lines · Peter Maydell
Quoted 13 lines · Daniel P. Berrangé
Quoted 7 lines · Thomas Huth
Maybe try to clean the folder first:
rm -r capstone
mkdir capstone
make git-submodule-updateIf that does not help, maybe try a completely fresh git checkout?
Rather than deleting stuff like that, it is best to use git to put your dir back to a clean state.
Quoted 6 lines
Quoted 2 lines
git submodule deinit --all --force git clean -f -x -dThat git clean line will blow away any untracked files in your entire tree, won't it? If so, better move anything you cared about somewhere else first...
Yes, git clean blows away everything that isn't tracked.
Regards,
Daniel
Signature · 3 lines
|: 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 :|
Quoted 65 lines · Thomas Huth
Quoted 8 lines · Programmingkid
Quoted 8 lines · Thomas Huth
Quoted 4 lines · Programmingkid
Quoted 4 lines · Thomas Huth
On 19/04/2019 15.44, G 3 wrote:
[...]
Quoted 29 lines
Quoted 20 lines
Quoted 20 lines
Quoted 19 lines
Quoted 10 lines
Thank you for replying. Capstone comes with QEMU? Every time I try to compile QEMU I see an error relating to Capstone not being on my system. Why do you feel that disabling Capstone by default is not a good idea?
Here is the error message I see when compiling QEMU:
CHK
version_gen.h
make[1]: *** No rule to make target `/Users/John/qemu-git/capstone/libcapstone.a'. Stop.
make: *** [subdir-capstone] Error 2I assume you're using a git checkout here, right? For git checkouts, the
Makefileshould take care of calling thescripts/git-submodule.shscript which should initialize the submodule in the capstone directory.What's the content of your .git-submodule-status file? What does "configure" say about capstone support on your system?
Thomas
Quoted 8 lines
Quoted 4 lines
Yes I use a git checkout.
This is the contents of my .git-submodule-status file:
#!/bin/sh[...]
That were the contents of
scripts/git-submodule.sh. I meant the hidden file .git-submodule-status in the main directory.Quoted 6 lines
This is it:
88f18909db731a627456f26d779445f84e449536dtc (v1.4.7)f0da6726207b740f6101028b2992f918477a4b08slirp (v4.0.0-rc0-25-gf0da672)b64af41c3276f97f0e181920400ee056b9c88037tests/fp/berkeley-softfloat-3 (heads/master)5a59dcec19327396a011a17fd924aed4fec416b3tests/fp/berkeley-testfloat-3 (remotes/origin/HEAD)6b3d716e2b6472eb7189d3220552280ef3d832ceui/keycodemapdb (heads/master-4-g6b3d716)There should be an entry for capstone in here, too. :-/
Quoted 5 lines
Quoted 5 lines
Quoted 4 lines
I did a 'make clean' followed by a 'make distclean'. Then tried building again using this command line:
./configure --target-list=ppc-softmmu,i386-softmmu,x86_64-softmmu make -j 4
Quoted 8 lines
Quoted 2 lines
That should normally populate the capstone directory. What happens if you run "make git-submodule-update" directly?
Here is the result:
$ make git-submodule-update make[1]: Nothing to be done for `all'. make[1]: *** No rule to make target `/Users/John/Documents/Development/Projects/Qemu/qemu-git/capstone/libcapstone.a'. Stop. make: *** [subdir-capstone] Error 2
Quoted 6 lines
Apparently the submodule update is not working right for you. What do you get when you run:
git submodule update capstone
?
Nothing appears to happen. When I try to make QEMU I still see the same error about no rule to make target libcapstone.a.
Quoted 8 lines
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
I took a look at the capstone folder. There is no 'make' file in this folder. Should there be one?
Yes, the capstone folder should be populated automatically. Is it completely empty for you?
It isn't empty. All I see are two folders: obj and docs.
Quoted 7 lines
Maybe try to clean the folder first:
rm -r capstone
mkdir capstone
make git-submodule-updateIf that does not help, maybe try a completely fresh git checkout?
That did it! The capstone folder is now fully populated. Thank you so much.