| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
| |
The mpfr project is now using git. Update the repository field
accordingly.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
|
|
|
|
|
|
|
| |
The GCC project has been using git for a while now. Update the
repository field accordingly.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
|
|
|
|
| |
Signed-off-by: Dima Krasner <dima@dimakrasner.com>
|
|
|
|
|
|
| |
Remove patches applied upstream we no longer need to maintain here.
Signed-off-by: Hans-Christian Noren Egtvedt <hegtvedt@cisco.com>
|
|
|
|
|
|
|
|
| |
Modern versions of the 'file' utility give different output for position
dependent and position independent executables. The populate tool should
consider both types.
Signed-off-by: Johan Levin <johan13@gmail.com>
|
|
|
|
| |
Signed-off-by: Dima Krasner <dima@dimakrasner.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Newer GCC versions trigger warnings on older GLIBC versions. GLIBC 2.29
is warning free with GCC9. GLIBC 2.31 is warning free with GCC10. GLIBC
2.34 is warning free with GCC11.
Add milestones for 2.31 and 2.34 and use those to set the default value
for GLIBC_ENABLE_WERROR based on the GCC version.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bring in the following changes
- Fix a deflate bug when using the Z_FIXED strategy that can result in
out-of-bound accesses.
- Fix a deflate bug when the window is full in deflate_stored().
- Speed up CRC-32 computations by a factor of 1.5 to 3.
- Use the hardware CRC-32 instruction on ARMv8 processors.
- Speed up crc32_combine() with powers of x tables.
- Add crc32_combine_gen() and crc32_combine_op() for fast combines.
Drop two patches that have been applied upstream and regenerate the
remaining two.
Fixes #1708
Signed-off-by: Chris Packham <judge.packham@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On my Ubuntu machine (with `dash` version `0.5.10` and `bash` version `5.0.17`),
I would get errors such as the following:
```
crosstool-ng/scripts/functions: line 730: [: !=: unary operator expected
```
This is generally because a variable is not set, and expands to an empty string
causing the test operator to mis-parse the expression. To fix this, I have
added quotes around the variable.
Signed-off-by: Elliot Saba <staticfloat@gmail.com>
|
|
|
|
|
|
| |
meson and ninja are needed to build picolibc.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Fixes 1.7.4 issue with recent meson versions which error on
'descrption' typo.
* Positional parameters (%$1d) in printf/scanf
* Lots (and lots) of math library exception/errno fixes; now tested against
glibc test suite.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
Posix threads are enabled in the x86_64-w64-mingw32 sample having them
enabled in i686-w64-mingw32 makes things consistent for these targets.
Fixes #1696
Signed-off-by: Chris Packham <judge.packham@gmail.com>
|
| |
|
| |
|
|
|
|
|
|
|
| |
Bring in upstream fix for gcc outputting an incorrect .machine
directive.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
|
|
|
|
|
|
|
|
|
| |
Some versions of GCC emit a .machine directive near the start of the
compiler's assembly output that overrides the CPU passed on the command
line. Bring in an upstream change for binutils that works around the
problem.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Prior to commit bbc4db13 ("kconfig: Sync with upstream v4.18") we used
the macros CURSES_LOC and MENU_LOC to tell us where curses.h and menu.h
were installed. Restore this behaviour so that we can deal with some of
the odd places that the curses headers end up.
Fixes #1403
Signed-off-by: Chris Packham <judge.packham@gmail.com>
|
|
|
|
|
|
| |
Backport of https://github.com/gcc-mirror/gcc/commit/cc1e28878a228b6c4a0872e56d97ac88971b7725
Signed-off-by: Kittenberger Iván <ivanka2012@gmail.com>
|
|
|
|
|
|
|
| |
Rather important option for arm cortex toolchains supporting c++,
avoids pulling in all printf/iostream code by default.
Signed-off-by: Norbert Lange <nolange79@gmail.com>
|
|
|
|
| |
Signed-off-by: Norbert Lange <nolange79@gmail.com>
|
|
|
|
| |
Signed-off-by: Norbert Lange <nolange79@gmail.com>
|
|
|
|
| |
Signed-off-by: Norbert Lange <nolange79@gmail.com>
|
|
|
|
|
|
|
|
|
| |
libdebuginfod is incompatible with static linking so pass
--without-debuginfod when CT_STATIC_TOOLCHAIN is selected.
Fixes #1683
Signed-off-by: Chris Packham <judge.packham@gmail.com>
|
|
|
|
|
|
|
|
| |
CentOS6 has reached EOL so now glibc-2.12.1 can be marked as obsolete.
This also means the last glibc-ports version (and glibc-ports itself)
obsolete as well. These will be removed after the next release.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
|
|
|
|
|
|
|
|
|
|
| |
Support for bionic was dropped by GCC some time ago. There are patches
for older GCC versions but those are difficult to maintain and the
version of the android-ndk they support is of little use. Mark all of
the existing bionic support as obsolete so it can be removed after the
next release.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
|
|
|
|
|
|
|
|
|
| |
strace maintains backwards compatibility with older kernels so there is
no need to keep multiple versions of strace. Versions 5.0 to 5.14
weren't present in the crosstool-ng-1.24 release so remove them directly
instead of marking them as obsolete.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
|
|
|
|
|
|
|
|
|
| |
strace maintains backwards compatibility with older kernel versions so
there's no particular reason to keep many versions of strace around.
Mark the versions that were present in the 1.24 release as obsolete.
They will be remove following the next release.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
|
|
|
|
| |
Signed-off-by: Artem Panfilov <artemp@synopsys.com>
|
|
|
|
| |
Signed-off-by: Artem Panfilov <artemp@synopsys.com>
|
|
|
|
| |
Signed-off-by: Artem Panfilov <artemp@synopsys.com>
|
|
|
|
|
|
| |
https://lists.strace.io/pipermail/strace-devel/2022-January/010884.html
Signed-off-by: Chris Packham <judge.packham@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add 5.16.9
Bump 5.15.2 -> 5.15.23
Bump 5.10.79 -> 5.10.100
Bump 5.4.159 -> 5.4.179
Bump 4.19.217 -> 4.19.229
Bump 4.9.290 -> 4.9.301
Bump 4.4.292 -> 4.4.302
Signed-off-by: Chris Packham <judge.packham@gmail.com>
|
|\
| |
| | |
Updates to make `ct-ng build-all` pass
|
| |
| |
| |
| |
| |
| |
| |
| | |
This refreshes the line numbers, removes any fuzz (which would make any
future forward ports easier) and standardizes the patch/file headers
(which makes them easier to read).
Signed-off-by: Alexey Neyman <stilor@att.net>
|
| |
| |
| |
| |
| |
| |
| | |
This fixed some typos in the checksum files (please don't edit them
manually, this is error-prone!)
Signed-off-by: Alexey Neyman <stilor@att.net>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
To avoid proliferation of versions, I suggest the following policy: the
oldest LTS release still receiving maintenance updates + the most recent
release for distributions that offer LTS releases.
For CentOS, this means CentOS7 and CentOS Stream 9 (since CentOS are all
"long-term support", this is just the oldest and the newest among
currently supported).
For Ubuntu, this means Ubuntu 18.04 (previous LTS are in "security fixes
only" mode) and Ubuntu 21.10. Recent Ubuntu attempts to be interactive
during the configuration of tzdata, required some additional setup.
In the common installation script, the logic for handling a
configured/built local directory breaks if `gmake` is detected as the
make binary; `make distclean` then fails inside the container because
not all systems have `gmake` symlink. Remove that attempt of a
workaround completely, just require that the host directory is clean.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
| |
| |
| |
| |
| |
| |
| | |
Otherwise, it tries to link against libgcc_eh which is not available
until the final compiler (or previously, the pass-2 compiler) is built.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
With libc_headers step before pass-1, there is no need to distinguish
pass-1 and pass-2; they are configured identically (note that with the
current configuration, core pass-2 is only used for win32 - hence, uses
build_libgcc=yes and mode=static).
Signed-off-by: Alexey Neyman <stilor@att.net>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
After 557b9d4, libc_start_files and libc_main steps are performed one
after another. It doesn't make sense, especially since some of the libcs
(glibc, uClibc-ng) go to great lengths to first install start files in
the first step, libc_start_files, only to remove them immediately in the
second step, libc_main.
Current build steps also break in the xtensa newlib configurations, as
it needs to install the custom xtensa headers before building the libgcc
and after 557b9d4, the headers are not installed before libgcc is built
in pass-1.
Therefore, finish what 557b9d4 mentioned but did not do: move header
installation into a new step, libc_headers, and combine libc_start_files
and libc_main into a single step.
This also allows to combine the core pass-1/pass-2 steps, to be done in
a subsequent commit.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
| |
| |
| |
| | |
Signed-off-by: Alexey Neyman <stilor@att.net>
|
| |
| |
| |
| |
| |
| |
| | |
Recent changes introduced a mixture of tabs/spaces that result in broken
indentation in multiple places.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
| |
| |
| |
| |
| |
| |
| | |
Newer gettext is incompatible with uClibc-NG in cross-compilation, see
the comment in the code.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes the x86_64-multilib-linux-uclibc,powerpc-unknown-elf canadian
cross example (which currently breaks because the gnulib example assumes
SIGSTKSZ is constant while recent libcs started defining it as a
sysconf(...) call.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
| |
| |
| |
| |
| |
| | |
Refer to the comments in the code for the reason.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This was originally an upgrade from 11.1 to 11.2 that fixed moxie-*
samples affected by PR sim/28302. GDB 11.2 landed independently on
master, so just remove 11.1 (one release per upstream branch, please, we
already have lots of version/architecture/host permutations to test).
Signed-off-by: Alexey Neyman <stilor@att.net>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Starting with GDB9, the release number is only two numbers (with the
last being patchlevel). Therefore, keep two numbers for releases 8 and
below, but just a single number for 9 and up.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Starting with GDB10, it requires support for std::future<> in the
compiler. Such support has not been available on some architectures
until GCC9 (see PR 64735). I haven't determined the exact list of
affected architectures, so decided to make it a broad dependency: for
GDB10+, you need GCC9+.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
| |
| |
| |
| | |
Signed-off-by: Alexey Neyman <stilor@att.net>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Restrict kernel to 5.11 and below (support for this arch has been
dropped in 5.12); rename the sample to match its name as printed by
`ct-ng show-tuple` (otherwise, `make saveconfig` does not update the
sample's configuration).
Signed-off-by: Alexey Neyman <stilor@att.net>
|