Linking dynamically against libbfd results in a non-portable application
binary and is generally frowned upon by distributions: Debian forbids it
explicitly and on Gentoo, it results in a failure at run-time:
./lkvm: error while loading shared libraries: libbfd-2.22.so: cannot
open shared object file: No such file or directory
Avoid these problems by linking statically instead.
Signed-off-by: Will Deacon <will.dea...@arm.com>
---
tools/kvm/Makefile | 5 -----
1 files changed, 0 insertions(+), 5 deletions(-)
diff --git a/tools/kvm/Makefile b/tools/kvm/Makefile
index 23a7c40..44a55c2 100644
--- a/tools/kvm/Makefile
+++ b/tools/kvm/Makefile
@@ -171,11 +171,6 @@ endif
# both and only build those that link!
FLAGS_BFD := $(CFLAGS) -lbfd
-ifeq ($(call try-cc,$(SOURCE_BFD),$(FLAGS_BFD)),y)
- CFLAGS_DYNOPT += -DCONFIG_HAS_BFD
- OBJS_DYNOPT += symbol.o
- LIBS_DYNOPT += -lbfd
-endif
ifeq ($(call try-cc,$(SOURCE_BFD),$(FLAGS_BFD) -static),y)
CFLAGS_STATOPT += -DCONFIG_HAS_BFD
OBJS_STATOPT += symbol.o
--
1.7.4.1
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
