From: "Philippe Mathieu-Daudé" <1912059@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1912059] Re: capstone link failure building linux-user static
Date: Sun, 09 May 2021 15:48:10 -0000 [thread overview]
Message-ID: <162057529038.9997.17076161694635368660.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 161081170825.23111.15517151874905086702.malonedeb@soybean.canonical.com
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
** Changed in: qemu
Status: Incomplete => Invalid
** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #238
https://gitlab.com/qemu-project/qemu/-/issues/238
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1912059
Title:
capstone link failure building linux-user static
Status in QEMU:
Invalid
Bug description:
$ ../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).
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1912059/+subscriptions
prev parent reply other threads:[~2021-05-09 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 15:41 [Bug 1912059] [NEW] capstone link failure building linux-user static Philippe Mathieu-Daudé
2021-04-22 4:24 ` [Bug 1912059] " Thomas Huth
2021-05-09 15:48 ` Philippe Mathieu-Daudé [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=162057529038.9997.17076161694635368660.malone@chaenomeles.canonical.com \
--to=1912059@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.