From 59fe21c468d852a08847a8bcb62dea56408b510e Mon Sep 17 00:00:00 2001 From: Waldemar Brodkorb Date: Fri, 3 Oct 2014 06:11:32 +0200 Subject: disable linkage of gcc_eh As recently discussed on the uClibc mailing list here: http://lists.uclibc.org/pipermail/uclibc/2014-September/048659.html I think it is not required for gcc 4.8.3, which is default in f.e. OpenADK. Tested with a DODEBUG build for x86. --- Rules.mak | 4 ---- 1 file changed, 4 deletions(-) (limited to 'Rules.mak') diff --git a/Rules.mak b/Rules.mak index d6a225461..3cc38f87b 100644 --- a/Rules.mak +++ b/Rules.mak @@ -822,11 +822,7 @@ ASFLAGS += $(ASFLAG_--noexecstack) LIBGCC_CFLAGS ?= $(CFLAGS) $(CPU_CFLAGS-y) $(eval $(call cache-output-var,LIBGCC,$(CC) $(LIBGCC_CFLAGS) -print-libgcc-file-name)) -$(eval $(call cache-output-var,LIBGCC_EH,$(CC) $(LIBGCC_CFLAGS) -print-file-name=libgcc_eh.a)) -# with -O0 we (e.g. lockf) might end up with references to -# _Unwind_Resume, so pull in gcc_eh in this case.. LIBGCC_DIR:=$(dir $(LIBGCC)) -LIBGCC += $(if $(DODEBUG),$(LIBGCC_EH)) # moved from libpthread/linuxthreads ifeq ($(UCLIBC_CTOR_DTOR),y) -- cgit v1.2.3