crosstool-ng/samples/sh4-unknown-linux-gnu/crosstool.config

CT_LOCAL_TARBALLS_DIR="${HOME}/src"
CT_SAVE_TARBALLS=y
CT_LOG_EXTRA=y
CT_ARCH_sh=y
CT_ARCH_SH_SH4=y
CT_KERNEL_linux=y
CT_BINUTILS_PLUGINS=y
CT_CC_GCC_V_4_9_3=y
CT_CC_LANG_CXX=y
CT_DEBUG_gdb=y
# CT_GDB_CROSS_PYTHON is not set
Make Super-H finally compile a complete (C-only) toolchain: - new, un-tested patches - an sh4 sample to work on, and to try to reproduce later. /trunk/patches/glibc/2.7/250-sh-chop-linux-version.patch \| 49 49 0 0 ++ /trunk/patches/glibc/2.7/240-sh-lowlevellock-asm.patch \| 56 56 0 0 +++ /trunk/patches/glibc/2.7/270-sh-fix-procfs.patch \| 11 11 0 0 + /trunk/patches/glibc/2.7/280-sh-fix-kernel-heders-location.patch \| 23 23 0 0 + /trunk/patches/glibc/2.7/260-sh-syscall-error-path.patch \| 26 26 0 0 + /trunk/samples/sh4-unknown-linux-gnu/crosstool.config \| 311 311 0 0 ++++++++++++++ /trunk/samples/sh4-unknown-linux-gnu/reported.by \| 3 3 0 0 + 7 files changed, 479 insertions(+) 2008-10-22 20:50:10 +00:00			`CT_LOCAL_TARBALLS_DIR="${HOME}/src"`
			`CT_SAVE_TARBALLS=y`
			`CT_LOG_EXTRA=y`
			`CT_ARCH_sh=y`
			`CT_ARCH_SH_SH4=y`
			`CT_KERNEL_linux=y`
samples: update sh4 sample Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> 2014-08-31 16:53:13 +00:00			`CT_BINUTILS_PLUGINS=y`
Fix sh4-unknown-linux-gnu sample. The issue with this sample is that the sh4-* targets in GCC do not implement __builtin_trap() function. Starting with release 5.1, GCC inserts abort() calls where NULL pointers are dereferenced. The elf/dl-conflict.c in glibc is one such place: it calls elf_machine_rela with NULL `sym' pointer. This causes an undefined `abort' symbol to appear in the object file and as a result, pulls in some files during the linking of the dynamic loader that are not supposed to. Eventually, it results in link error due to multiple definitions of _itoa and some other symbols. The right fix would be to implement __builtin_trap() for sh4 in GCC. A workaround would be adding -fno-delete-null-pointer-checks to CFLAGS-dl-conflict.c in elf/Makefile. Until either of these happens, though, pin the GCC version to 4.9.3 - the last that did not generate `abort' calls. Note that the version where GCC started to generate `abort' calls is apparently different for different architectures; the issue in [1] was reported against GCC 4.9. References: [1] https://www.sourceware.org/ml/libc-alpha/2014-10/msg00807.html (similar issue on HP-PA which was resolved by implementing __builtin_trap) 2015-09-30 23:31:27 +00:00			`CT_CC_GCC_V_4_9_3=y`
samples: update sh4 sample Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> 2014-08-31 16:53:13 +00:00			`CT_CC_LANG_CXX=y`
			`CT_DEBUG_gdb=y`
			`# CT_GDB_CROSS_PYTHON is not set`