Age | Commit message (Collapse) | Author | Files | Lines |
|
Ltrace
|
|
Having *.la in the installation directory breaks ltrace: in ltrace,
libtool somehow considers libsupc++ to be an "accessory library" and
does not add -lsupc++ to the link flags. Neither Ubuntu, nor RedHat
include *.la files into their packages for libstdc++.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
This reverts commit a3bb2aeb4445bef4250acaaff99fc8dbb0599f8b.
|
|
musl-libc: backport gcc-6 musl support, add gdb and strace patches
|
|
Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
|
|
This gets gcc and friends working with musl-libc.
GDB and Strace patches come from openwrt.
Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
|
|
bhundven/binutils_gold_conflicts_with_static_toolchain
binutils: Gold conflicts with Static Toolchain
|
|
Fix avr sample
|
|
linux: Update linux kernel versions
|
|
Update current stable and long-term releases:
* 4.2 -> 4.2.3
* 4.1.6 -> 4.1.10
* 3.18.20 -> 3.18.22
* 3.14.51 -> 3.14.54
* 3.12.47 -> 3.12.49
* 3.10.87 -> 3.10.90
* 3.4.108 -> 3.4.109
* 3.2.71 -> 3.2.72
* 3.6.32.67 -> 3.6.32.68
Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
|
|
musl-libc: update musl-libc mainline to 1.1.12
|
|
Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
|
|
The gold linker cannot currently be built in a static toolchain build.
This may get fixed in a future version of crosstool-NG.
Also, there is a bit of weirdness here. versions of binutils >= 2.21
have GOLD (BINUTILS_HAS_GOLD), but that doesn't mean it should be used.
For instance, if the architecture is not supported.
So with that, we create a new hidden option: BINUTILS_GOLD_SUPPORT
Which in turn depends on BINUTILS_GOLD_SUPPORTS_ARCH, BINUTILS_HAS_GOLD,
and not STATIC_TOOLCHAIN... then replace anything that previously
depended on BINUTILS_HAS_GOLD with our new BINUTILS_GOLD_SUPPORT option.
This closes #210
Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
|
|
Fix option names in powerpc-e500v2 sample.
|
|
Fix link error in arm/uclibc with GCC 5.x
|
|
Missing include in glibc-2.22 for sparc32/nptl.
|
|
Trivial avr32 fix: name of config option has changed
|
|
Restore 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)
|
|
|
|
Options were renamed. However, matching current option names result
in a compile error for strfmon_l.o in glibc: GCC 4.6 detects an
unitialized variable in its own va_arg() implementation. Likely,
an older GLIBC was used when this sample was submitted - which did
not provide -Werror in CFLAGS.
Thus, use most recent GCC (5.2.0) and revert GLIBC_FORCE_UNWIND to
its default value, 'y' (as forced unwind is required with this version).
|
|
- Incompatible ISL/CLooG were requested by config after newer releases
of both were brought in.
- Consistency with other samples: save tarballs (which will avoid
downloading them each time from Travis), extra logging.
|
|
|
|
This should ideally be upstreamed to uclibc maintainers, but with the
last release more than 3 years ago, I wouldn't hold my breath for a
fix being released any time soon.
|
|
Fix a typo in the documentation
|
|
Using "all" and "install" targets in do_gcc_core_backend if configured
|
|
Remove CC_GDB_CUSTOM from the version choice
|
|
Restore blackfin sample
|
|
Replace "now" with "know."
|
|
- New configurations:
- CC_GCC_TARGET_FINAL:
Use the default targets "all" and "install" for the final compiler for
bare metal.
- Adding parameter "build_step" to function do_gcc_core_backend:
do_gcc_core_backend is used for the core compiler and in case of bare metal
for the final compiler, too. To have better control over the parameters for
the final compiler "build_step" is used.
- Used for proper logging.
- Use CT_CC_GCC_CORE_EXTRA_CONFIG_ARRAY or CT_CC_GCC_EXTRA_CONFIG_ARRAY.
- If CT_CC_GCC_TARGET_FINAL is set and the final compiler is build then the
make targets for the final compiler are used ("all", "install").
Signed-off-by: Jasmin Jessich <jasmin@anw.at>
|
|
Synchronize CC_GCC_USE_LTO parameter setting II
|
|
Add additional environment variables for gcc build.
|
|
Adding missing if/else blocks in do_gcc_core_backend.
|
|
Manage Travis-CI build
|
|
Signed-off-by: Jasmin Jessich <jasmin@anw.at>
|
|
This reverts commits:
* d6413fe29fbdcd72a04b3d5820ba2e134dbaf558.
* 4f266e1a8c78cec2c425b17784576db56125bbbd.
Signed-off-by: Jean-Marie Lemetayer <jeanmarie.lemetayer@gmail.com>
|
|
Signed-off-by: Jean-Marie Lemetayer <jeanmarie.lemetayer@gmail.com>
|
|
This allows to:
* override configuration
* deal with travis-ci timing restrictions
Signed-off-by: Jean-Marie Lemetayer <jeanmarie.lemetayer@gmail.com>
|
|
|
|
Pin GCC to 4.5.3 and binutils to 2.22, the last versions working. There
are multiple bugs affecting bfin configuration; while [3] is fixed on
trunk in GCC (but not backported to gcc-5-release branch yet), [1] and
[2] do not have fixes yet.
References:
[1] https://sourceware.org/bugzilla/show_bug.cgi?id=17334 (binutils bug)
[2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47779 (gcc bug #1)
[3] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55144 (gcc bug #2)
|
|
config: Tone down automated build logs
|
|
I forgot that the logs must stay small, and if they fail we'll grab the
last few hundered lines.
Note, the logs must stay smaller then 4M.
Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
|
|
configure: Add automated build option
|
|
This commit introduces a configure time option to let the build know
that this is going to be an automated build.
This forces the build to disable the progress bar, log tool warnings,
and force the log level to debug.
Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
|
|
Remove ltrace from samples
|
|
As of right now, ltrace fails to build. To get CI happy, lets just
disable it!
When we fix ltrace, just revert this change.
This is also in reference to bug #115
Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
|
|
from do_gcc_core_backend, by adding "--enable-lto"/"--disable-lto".
Signed-off-by: Jasmin Jessich <jasmin@anw.
|
|
Fixed travis-ci environment setting
|
|
Signed-off-by: Jasmin Jessich <jasmin@anw.at>
|