Browse Source

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.
Waldemar Brodkorb 9 years ago
parent
commit
59fe21c468
1 changed files with 0 additions and 4 deletions
  1. 0 4
      Rules.mak

+ 0 - 4
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)