mirror of
https://github.com/crosstool-ng/crosstool-ng.git
synced 2025-02-21 09:21:52 +00:00
52203df900
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)
Crosstool-NG 
Crosstool-NG follows the autoconf dance. So, to get you
kick-started, just run:
./configure --help
If you are using a development snapshot, you'll have to create the configure script, first. Just run:
./bootstrap
You will find the documentation in the directory docs.
Here is a quick overview of what you'll find there:
- Table of content
- Introduction
- Installing crosstool-NG
- Configuring a toolchain
- Building the toolchain
- Using the toolchain
- Toolchain types
- Contributing
- Internals
- Credits
- Known issues
- Misc. tutorials
You can also point your browser at: http://crosstool-ng.org
Aloha!