This makes the options necessary to run the gcc test suite
configurable in the crosstool-ng config file.
That includes the ability to run the test suite using qemu instead of
on a remote host.
Signed-off-by: Keith Packard <keithp@keithp.com>
The default for wide char support has changed in ncurses-6.5. This
causes build failures for gdb. Pass --disable-widec to prevent the build
errors.
Fixes#2292, #2294
Signed-off-by: Chris Packham <judge.packham@gmail.com>
This patch defines `WIN32_LEAN_AND_MEAN` before the `windows.h` include
statements to avoid name clashes with the `abort()` member function in
`IXMLDOMDocument`, which would now be pulled in via `msxml.h` without
the `WIN32_LEAN_AND_MEAN` definition.
Signed-off-by: Oliver Old <mail@oold.dev>
A static toolchain by definition can't load plugins and GCC will reject
the --enable-plugin configure option if we're trying to build a static
toolchain.
Fixes#2288
Signed-off-by: Chris Packham <judge.packham@gmail.com>
Add a patch from upstream GMP that updates some custom configure checks
for C23 compatibility (gnu32 will be the default for GCC 15).
Reported-by: Marc Poulhiès <dkm@kataplop.net>
Signed-off-by: Chris Packham <judge.packham@gmail.com>
An older version of MPC had issues with some versions of MPFR. We don't
actually have either version of these packages anymore so we no longer
need these milestones.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
Previous commits added selects so that the nios2 architecture only used
GDB/GLIBC versions that still support it however these weren't qualified
leading to kconfig complaints such as
WARNING: unmet direct dependencies detected for GLIBC_REQUIRE_older_than_2_41
Depends on [n]: LIBC_GLIBC_SHOW [=n]
Selected by [y]:
- ARCH_NIOS2 [=y] && GEN_CHOICE_ARCH [=y]
Qualify these selects with if DEBUG_GDB and if LIBC_GLIBC to stop the
complaints.
Fixes: 9d91cebe ("gdb: Add 16.1")
Fixes: 87605d65 ("glibc: Add 2.41")
Signed-off-by: Chris Packham <judge.packham@gmail.com>
The latest gettext has problems building this configuration. Pin the
version to gettext-0.22.5 which works fine.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
Some canadian configs that use uclibc are pinned to gettext-0.20.1. We
need to update some of the configure checks to avoid issues with newer
versions of GCC.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
Add newly released mold version 2.36.0 from upstream
https://github.com/rui314/mold
New Features
- The --package-metadata=<string> option has been added to embed a given
string into the .note.package section. This option is designed for
build scripts that generate binary packages, such as .rpm or .deb, to
include package metadata in each executable. It simplifies the process
of identifying the corresponding package for a given executable or
core file. (7ddc8f4)
- [ARM][PowerPC] We've improved the algorithm for creating range
extension thunks to reduce memory usage and improve speed. For
example, linking clang-19 for ARM64 is now ~7% faster than before.
(9fc0ace)
- [RISC-V][LoongArch] We've improved the algorithm for code-shrinking
linker relaxation to reduce memory usage and improve speed. For
example, linking clang-19 for RISC-V is now ~4% faster than before.
(3234d88)
Bug Fixes and Compatibility Improvements
- mold created a bad relocation for an IFUNC if the linker's output file
type was a shared library and the symbol was exported. This bug could
cause a segmentation fault of a linked program. The problem has now
been fixed. (a297859)
- [RISC-V] mold could produce incorrect code as a result of
code-shrinking relaxation for the R_RISCV_HI20 relocation. That type
of relocation was used rarely because it is not PC-relative. That
being said, if your program used the relocation, and the relocation
targets were at a low address (from 0x1f800 to 0x20000), your program
would crash at runtime due to the linker's bug. The issue has now been
resolved. (eec3f6b)
- [RISC-V][LoongArch] When the linker removed instructions from a
function as a result of code-shrinking relaxation, the function
symbol's size in the output file should be updated to reflect the
result of relaxation, even though doing it is mostly cosmetic. mold
did not do that. Now, mold sets correct sizes to output function
symbols. (e6345d5)
- [LoongArch] Binaries linked with mold now work on 64 KiB page systems.
Previously, only up to 16 KiB pages were supported. (2d7b6b2)
- [s390x] The s390x processor-specific ABI requires the linker to
reserve the first three slots of the .got section for the runtime.
mold, however, reserved only two slots and used the third for itself.
Even though we did not observe issues in the wild, it was a violation
of the psABI. The problem has now been fixed. (dfce2fc)
Signed-off-by: Hans-Christian Noren Egtvedt <egtvedt@samfundet.no>
MUSL's or1k support lacks definitions for elf_gregset_t which leads to
failures like
[ERROR] sysroot/usr/include/sys/procfs.h:29:9: error: 'elf_gregset_t' does not name a type; did you mean 'gregset_t'?
[ERROR] sysroot/usr/include/sys/procfs.h:54:9: error: 'elf_gregset_t' does not name a type; did you mean 'gregset_t'?
[ERROR] sysroot/usr/include/sys/procfs.h:55:9: error: 'elf_fpregset_t' does not name a type
Disable GDB support in the or1k-unknown-linux-musl config.
Fixes#2266
Signed-off-by: Chris Packham <judge.packham@gmail.com>
There is subtle difference between our CTNG_PYTHON and the AX_PYTHON on
which it is based. The latter uses AC_CHECK_PROGS() which sets
PYTHON_BIN to the name of the executable. We use AC_PATH_PROGS() which
sets PYTHON_BIN to the full path of the executable.
Because the name of the executable is the same as the library AX_PYTHON
uses this when looking for the library with AC_CHECK_LIB() which magics
itself into a linker flag like `-lpython3.11` but our version ends up
with a nonsensical `-l/usr/bin/python3.11` so the check fails and we
keep iterating repeating the same wrong check for every tested python
version.
We can't just switch to using AC_CHECK_PROGS() because we do want to use
the variable set by AC_PATH_PROGS() to set the full path in paths.sh.
Ultimately we could probably switch to using the upstream AX_PYTHON
macro (https://www.gnu.org/software/autoconf-archive/ax_python.html) and
figure out a better way of getting the full path of the exectuable but
for now add an extra AC_CHECK_PROGS() to set a different variable and
use that for AC_CHECK_LIB().
Signed-off-by: Chris Packham <judge.packham@gmail.com>
Update the ol7u9 configs to use versions of isl and cloog that work with
the version of GCC that oracle uses. Add a note that these configs are
obsolete. They will be dropped after the next release.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
Some obsolete cloog versions were dropped in commit 41d4583a ("cloog:
Remove obsolete versions"). Unfortunately the ol7-u9 configs don't work
with newer versions of cloog. For now reinstate this version, after the
next release we'll drop it again along with the ol7-u9 configs.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
Some obsolete isl versions were removed in commit 04dce680 ("isl: Remove
obsolete versions"). Unfortunately the ol7-u9 configs don't work with
newer versions of isl. For now reinstate this version, after the next
release we'll drop it again along with the ol7-u9 configs.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
When the bpf-unknown-none sample was added the target support was not in
a released version of binutils or gcc. The support has been in a few
versions of each of these for a while now. Update the sample to use
released versions instead of potentially unstable versions from
upstream.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
The custom uclibc has compile errors with GCC 14. Ignoring that even a
bare metal config fails to build (assembler errors in libgcc) with GCC
14. For now pin the sample config to GCC 13 since that seems to work.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
As per https://gcc.gnu.org/gcc-14/changes.html nios2 will be removed in
GCC 15. Even in GCC 14 we need to pass --enable-obsolete to allow this
target. Update our samples accordingly.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
This target is in GCC/binutils/Linux/Glibc/musl for a while.
Baremetal/glibc/musl toolchains are all build tested.
Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
When building picolibc as a companion library the configure step can end
up picking up certain headers from the build system which causes build
failures. Pass an appropriate --with-headers= to the GCC back end when
building picolibc as a companion library so that the correct headers are
detected by ./configure.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
When building for bare metal only do_gcc_core_backend() is used. In
order to support GCC plugins the --enable-plugin needs to be passed to
GCC's configure.
Fixes#2244
Signed-off-by: Chris Packham <judge.packham@gmail.com>
