From a1c10778092702f8856c1cc92126ef9801952d74 Mon Sep 17 00:00:00 2001 From: Peter Korsgaard Date: Sun, 2 Oct 2011 23:19:10 +0200 Subject: binutils: build host version statically Otherwise we end up with libbfd/libopcodes in host/usr/$BUILD/$TARGET/lib, used by the binaries. Unfortunately it also adds rpaths, which first look in the build directory before here, causing trouble if the toolchain is used outside BR (E.G. for a SDK) and the build directory location reused for another incompatible build (E.G. another ARCH), as the binutils binaries then end up using the wrong libs. Fix it by linking statically instead. Signed-off-by: Peter Korsgaard --- package/binutils/binutils.mk | 1 + 1 file changed, 1 insertion(+) (limited to 'package/binutils') diff --git a/package/binutils/binutils.mk b/package/binutils/binutils.mk index 2d60ce074..5123568ec 100644 --- a/package/binutils/binutils.mk +++ b/package/binutils/binutils.mk @@ -30,6 +30,7 @@ endif # We just keep the convention of "host utility" for now HOST_BINUTILS_CONF_OPT = --disable-multilib --disable-werror \ --target=$(REAL_GNU_TARGET_NAME) \ + --disable-shared --enable-static \ $(BR2_CONFIGURE_STAGING_SYSROOT) \ $(BINUTILS_EXTRA_CONFIG_OPTIONS) -- cgit v1.2.3