network: 0.611 permissions: 0.589 vnc: 0.539 other: 0.509 PID: 0.498 semantic: 0.490 performance: 0.479 device: 0.445 socket: 0.436 graphic: 0.407 files: 0.404 boot: 0.367 debug: 0.339 KVM: 0.290 capstone link failure building linux-user static $ ../configure --disable-system --static qemu 5.2.50 static build: YES capstone: system [...] $ make qemu-i386 [...] [478/478] Linking target qemu-i386 FAILED: qemu-i386 cc -o qemu-i386 libcommon.fa.p/hw_core_cpu.c.o libcommon.fa.p/disas_capstone.c.o libcommon.fa.p/disas_i386.c.o ... -Wl,--as-needed -Wl,--no-undefined -Wl,--whole-archive libhwcore.fa libqom.fa -Wl,--no-whole-archive -Wl,--warn-common -Wl,-z,relro -Wl,-z,now -static -m64 -fstack-protector-strong -Wl,--start-group libqemuutil.a subprojects/libvhost-user/libvhost-user-glib.a subprojects/libvhost-user/libvhost-user.a libhwcore.fa libqom.fa -lcapstone -lrt -pthread -lutil -lm -lgthread-2.0 -lglib-2.0 -lpcre -lgthread-2.0 -lglib-2.0 -lpcre -Wl,--end-group /usr/bin/ld: cannot find -lcapstone collect2: error: ld returned 1 exit status ninja: build stopped: subcommand failed. make: *** [Makefile:172: run-ninja] Error 1 $ rpm -ql capstone-devel /usr/include/capstone /usr/include/capstone/arm.h /usr/include/capstone/arm64.h /usr/include/capstone/capstone.h /usr/include/capstone/evm.h /usr/include/capstone/m680x.h /usr/include/capstone/m68k.h /usr/include/capstone/mips.h /usr/include/capstone/platform.h /usr/include/capstone/ppc.h /usr/include/capstone/sparc.h /usr/include/capstone/systemz.h /usr/include/capstone/tms320c64x.h /usr/include/capstone/x86.h /usr/include/capstone/xcore.h /usr/lib64/libcapstone.so /usr/lib64/pkgconfig/capstone.pc libcapstone.a seems detected by Meson but is not installed on the system (Fedora 32). The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now. If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience. This is an automated cleanup. This bug report has been moved to QEMU's new bug tracker on gitlab.com and thus gets marked as 'invalid' now. Please continue with the discussion here: https://gitlab.com/qemu-project/qemu/-/issues/238