crosstool-ng/patches/glibc/2.7/220-objdump_for_host.patch

diff -durN glibc-2.7.orig/Makerules glibc-2.7/Makerules
--- glibc-2.7.orig/Makerules	2007-08-26 04:18:03.000000000 +0200
+++ glibc-2.7/Makerules	2008-07-28 15:17:27.000000000 +0200
@@ -1203,6 +1203,9 @@
 # The include magic above causes those files to use this variable for flags.
 CPPFLAGS-nonlib = -DNOT_IN_libc=1
 
+ifneq ($(OBJDUMP_FOR_HOST),)
+OBJDUMP = $(OBJDUMP_FOR_HOST)
+endif
 
 ifeq ($(versioning),yes)
 # Generate normalized lists of symbols, versions, and data sizes.
Have the glibc build use the cross-objdump, rather than the host one. On some distros (eg. Fedora), the native objdump can not interpret objects not for the native system, and thus fail. This commit adds a new patch against glibc-2.7 that introduces OBJDUMP_FOR_HOST, wich, if set, overides the detected objdump. Note: bizarely enough, glibc already has code to detect the cross-objdump, but that does not work for an unknown reason... :-( /trunk/patches/glibc/2.7/220-objdump_for_host.patch \| 13 13 0 0 +++++++++ /trunk/scripts/build/libc_glibc.sh \| 37 21 16 0 +++++++++++++++------------ 2 files changed, 34 insertions(+), 16 deletions(-) 2008-07-31 09:08:33 +00:00			`diff -durN glibc-2.7.orig/Makerules glibc-2.7/Makerules`
			`--- glibc-2.7.orig/Makerules 2007-08-26 04:18:03.000000000 +0200`
			`+++ glibc-2.7/Makerules 2008-07-28 15:17:27.000000000 +0200`
			`@@ -1203,6 +1203,9 @@`
			`# The include magic above causes those files to use this variable for flags.`
			`CPPFLAGS-nonlib = -DNOT_IN_libc=1`

			`+ifneq ($(OBJDUMP_FOR_HOST),)`
			`+OBJDUMP = $(OBJDUMP_FOR_HOST)`
			`+endif`

			`ifeq ($(versioning),yes)`
			`# Generate normalized lists of symbols, versions, and data sizes.`