summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2020-11-01Merge branch 'keith-packard-picolibc-1.4.7'Chris Packham5-38/+5
2020-11-01Merge branch 'picolibc-1.4.7' of git://github.com/keith-packard/crosstool-ng ↵Chris Packham5-38/+5
into keith-packard-picolibc-1.4.7
2020-11-01Merge branch 'lancethepants-xlocale'Chris Packham1-1/+0
2020-11-01Merge branch 'xlocale' of git://github.com/lancethepants/crosstool-ng into ↵Chris Packham1-1/+0
lancethepants-xlocale
2020-10-27packages/picolibc: Update to version 1.4.7Keith Packard5-38/+5
New picolibc release has some useful bug fixes Signed-off-by: Keith Packard <keithp@keithp.com>
2020-10-18Merge pull request #1408 from abrodkin/topic-binutils-no-globChris Packham1-0/+4
binutils: Disable glob for better portability
2020-10-18Merge pull request #1407 from ↵Chris Packham1-2/+4
bagasme/local-patch-dir-description-clarify-example Clarify tree layout of local patches directory
2020-10-18Merge pull request #1402 from lancethepants/add_uclibc-ng_1.0.36Chris Packham2-0/+16
Add uClibc-ng 1.0.36
2020-10-15Don't remove XLOCALE support unconditionally.lancethepants1-1/+0
Signed-off-by: Lance Fredrickson <lancethepants@gmail.com>
2020-10-15Add uClibc-ng 1.0.36lancethepants2-0/+16
Signed-off-by: Lance Fredrickson <lancethepants@gmail.com>
2020-10-14binutils: Disable glob for better portabilityAlexey Brodkin1-0/+4
Since glibc 2.27 glob interface was changed [1] and so "glob" & "glob64" symbols require glibc 2.27+. For us that means if we build Binutils on a machine with glibc 2.27+ produced binaries won't be any longer usable on machines with older glibc. As an example [2]: build on Ubuntu 18.04 (with glibc 2.27) and try to run on CentOS 7.x (with glibc 2.17), you'll see this: ---------------------->8------------------- ldd ld ld: /lib64/libc.so.6: version `GLIBC_2.27' not found (required by ld) ---------------------->8------------------- Now given glob is not really used by Binutils itself (only needed by GDB) and we build Binutils & GDB separately let's make at least Binutils more portable. In theory we may even try to do the same hack for GDB forcing it to use imported glob implementation. But since GDB is now built strictly by C++ compiler we'll get waaay to many incompatibilities due to multiple changes of C++ ABI in between GCC 7.5 of Ubuntu 18.04 and GCC 4.8.5 of CentOS 7.x, so there's no point to even try. [1] https://sourceware.org/git/?p=glibc.git;a=commit;h=ccf970c7a77e86f4f5ef8ecc5e637114b1c0136a [2] https://github.com/zephyrproject-rtos/sdk-ng/issues/280 Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
2020-10-13Clarify tree layout of local patches directoryBagas Sanjaya1-2/+4
Currently the help for LOCAL_PATCH_DIR did not specify the tree layout of custom patches directory. This commit adds such explanation. For example, the bundled patches for GCC are placed under packages/gcc/<gcc-version>, thus custom (local) GCC patches should be placed under $LOCAL_PATCH_DIR/gcc/<gcc-version>. Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
2020-10-07Merge pull request #1400 from fvalette/fix-m4-build-for-mingw32-hostChris Packham1-0/+8
m4: fix build for mingw32 host
2020-10-06m4: fix build for mingw32 hostFlorent Valette1-0/+8
While building a canadian toolchain for windows host (any target), the build failed for m4 host companion_tool with a recent mingw-w64 (at least 7.0.0). m4 needs stack smashing protection which is not part of mingw-w64 c library and an explicit trigger to link w/ libssp is needed. Signed-off-by: Florent Valette <florent.valette@gmail.com>
2020-10-06Merge pull request #1398 from egtvedt/fix-glibc-2.32-version.hChris Packham2-0/+28
glibc: fix version 2.32 not setting correct version string
2020-10-05glibc: set glibc build system default_cflags emptyHans-Christian Noren Egtvedt1-0/+2
By setting glibc build system default_cflags to be empty before building, we will enforce the build system to only use the crosstool-ng CFLAGS when building glibc. Properly solves the issue identified in #1396. Signed-off-by: Hans-Christian Noren Egtvedt <hegtvedt@cisco.com>
2020-10-05glibc: fix version 2.32 not setting correct version stringHans-Christian Noren Egtvedt1-0/+26
Backport change from glibc upstream that defines RELEASE as stable instead of release. This will at least cause the default_cflags to be set to expected default values again. Ref issue #1396, although the bigger issue of respecting crosstool-ng CT_GLIBC_EXTRA_CFLAGS is most likely still not fixed. Signed-off-by: Hans-Christian Noren Egtvedt <hegtvedt@cisco.com>
2020-09-27Merge pull request #1391 from egtvedt/add-binutils-2.35.1Chris Packham12-12/+12
binutils: add version 2.35.1
2020-09-22binutils: add version 2.35.1Hans-Christian Noren Egtvedt12-12/+12
Bump to latest 2.35 minor release from upstream, now 2.35.1, replaces version 2.35. Signed-off-by: Hans-Christian Noren Egtvedt <hegtvedt@cisco.com>
2020-09-20Merge branch 'picolibc-multiarch' of ↵Chris Packham3-8/+8
git://github.com/keith-packard/crosstool-ng into master
2020-09-20Merge branch 'linux-version-bump' of ↵Chris Packham22-49/+57
https://github.com/cpackham/crosstool-ng into master
2020-09-20Merge branch 'continuous-integration' of ↵Chris Packham2-7/+14
https://github.com/cpackham/crosstool-ng into master
2020-09-20Merge branch 'general-package-patches' of ↵Chris Packham1-3/+5
git://github.com/foss-for-synopsys-dwc-arc-processors/crosstool-ng into master
2020-09-16picolibc: Use target architecture to drive picolibc configurationKeith Packard1-5/+5
This selects code matching the target architecture within picolibc. Signed-off-by: Keith Packard <keithp@keithp.com>
2020-09-16Map picolibc to suitable CT_TARGET_SYS valuesKeith Packard2-3/+3
picolibc is another bare-metal C library, and so should be mapped to CT_TARGET_SYS just like newlib does. Signed-off-by: Keith Packard <keithp@keithp.com>
2020-09-15linux: Add new versions and bump LTSChris Packham22-49/+57
Add 5.7.19 and 5.8.9. Bump 5.5.5 -> 5.5.19 Bump 4.19.105 -> 4.19.145 Bump 4.14.171 -> 4.14.198 Bump 4.9.214 -> 4.9.236 Bump 4.4.214 -> 4.4.236 Signed-off-by: Chris Packham <judge.packham@gmail.com>
2020-09-15Merge pull request #1387 from modbw/strace-updateChris Packham6-0/+12
Added strace 5.6, 5.7 and 5.8
2020-09-14Added strace 5.6, 5.7 and 5.8Matthias Weisser6-0/+12
2020-09-14CI: Add more architecturesChris Packham1-3/+13
Add arc, mips64, riscv32, riscv64, s390, sh, sparc and xtensa builds to CI job. Also add an arm-picolibc-eabi target. Signed-off-by: Chris Packham <judge.packham@gmail.com>
2020-09-14CI: Don't enable verbose outputChris Packham1-4/+0
We get the build log via the artifact upload so having it in the action output is redundant (it also tends to get suppressed anyway). Signed-off-by: Chris Packham <judge.packham@gmail.com>
2020-09-14config/libc: Extend glibc 2.32 workaround to include sparcChris Packham1-0/+1
Sparc seems to be affected by the same issues as powerpc64. Disable glibc warnings for sparc. Signed-off-by: Chris Packham <judge.packham@gmail.com>
2020-09-14Merge pull request #1386 from galak/gdb-9.2Chris Packham8-8/+8
gdb 9.2 support
2020-09-14Merge pull request #1384 from cpackham/glibc-2.32-configChris Packham1-1/+2
glibc: --enable-obsolete-rpc has been removed as of 2.32
2020-09-14Merge pull request #1379 from egtvedt/add-mpc-1.2.0-and-mpfr-4.1.0Chris Packham4-0/+20
Add support for mpc 1.2.0 and mpfr 4.1.0
2020-09-11gdb 9.2 supportKumar Gala8-8/+8
Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2020-09-10Patches: search package patches in the top package directoryMikhail Falaleev1-3/+5
Before patches for specific package were searched in packages/${pkg_name}/${version}. This means that with usage of custom version, patches wont be applied. This commit makes ct-ng search bundled patches also in packages/${pkg_name} directory. That means that we can put some patches in this directory, that will be applied to any version of this component.
2020-09-07glibc: --enable-obsolete-rpc has been removed as of 2.32Chris Packham1-1/+2
Make --enable-obsolete-rpc conditional on !CT_GLIBC_2_32_or_later as it's been removed from that version on. Signed-off-by: Chris Packham <judge.packham@gmail.com>
2020-09-06Merge branch 'cpackham-ci-status' into masterChris Packham1-0/+3
2020-09-06Merge branch 'ci-status' of https://github.com/cpackham/crosstool-ng into ↵Chris Packham1-0/+3
cpackham-ci-status
2020-09-06Merge branch 'pradghos-BR1_zlinux_cross_comp' into masterChris Packham8-9/+22
2020-09-06Merge branch 'BR1_zlinux_cross_comp' of ↵Chris Packham8-9/+22
git://github.com/pradghos/crosstool-ng into pradghos-BR1_zlinux_cross_comp
2020-09-06Merge branch 'jubalh-unused' into masterChris Packham1-2/+1
2020-09-06Merge branch 'unused' of git://github.com/jubalh/crosstool-ng into jubalh-unusedChris Packham1-2/+1
2020-09-06Merge branch 'dimkr-musl-update' into masterChris Packham2-0/+4
2020-09-06Merge branch 'musl-update' of git://github.com/dimkr/crosstool-ng into ↵Chris Packham2-0/+4
dimkr-musl-update
2020-09-06Merge branch 'keith-packard-picolibc' into masterChris Packham10-0/+308
2020-09-06Merge branch 'picolibc' of git://github.com/keith-packard/crosstool-ng into ↵Chris Packham10-0/+308
keith-packard-picolibc
2020-09-06Merge branch 'cpackham-powerpc64-glibc-2.32' into masterChris Packham2-1/+2
2020-09-03glibc: Don't build with -Werror for powerpc64+glibc-2.32Chris Packham2-1/+2
When building powerpc64+glibc-2.32 we see the following error: [ALL ] In file included from ../sysdeps/powerpc/powerpc32/power4/multiarch/wordcopy-ppc32.c:26, [ALL ] from ../sysdeps/powerpc/powerpc64/multiarch/wordcopy-ppc64.c:18: [ALL ] ../string/wordcopy.c: In function '_wordcopy_fwd_aligned': [ERROR] ../string/wordcopy.c:98:26: error: 'a1' may be used uninitialized in this function [-Werror=maybe-uninitialized] [ALL ] 98 | ((op_t *) dstp)[0] = a1; [ALL ] | ~~~~~~~~~~~~~~~~~~~^~~~ [ALL ] In file included from ../sysdeps/powerpc/powerpc64/power4/../../powerpc32/power4/memcopy.h:38, [ALL ] from ../sysdeps/powerpc/powerpc64/power4/memcopy.h:1, [ALL ] from ../string/wordcopy.c:23, [ALL ] from ../sysdeps/powerpc/powerpc32/power4/multiarch/wordcopy-ppc32.c:26, [ALL ] from ../sysdeps/powerpc/powerpc64/multiarch/wordcopy-ppc64.c:18: [ALL ] ../string/wordcopy.c: In function '_wordcopy_fwd_dest_aligned': [ERROR] ../sysdeps/generic/memcopy.h:72:61: error: 'a3' may be used uninitialized in this function [-Werror=maybe-uninitialized] [ALL ] 72 | #define MERGE(w0, sh_1, w1, sh_2) (((w0) << (sh_1)) | ((w1) >> (sh_2))) [ALL ] | ^~ This seems to only trigger for powerpc64. Other architectures build cleanly. For now avoid specifying -Werror for powerpc64+glibc-2.32. Signed-off-by: Chris Packham <judge.packham@gmail.com>
2020-09-01Add picolibc support [v2]Keith Packard10-0/+308
This adds support for using picolibc instead of newlib on embedded systems. Signed-off-by: Keith Packard <keithp@keithp.com> v2: Add check for meson and ninja Sync option default values with current picolibc defaults Remove xtensa sys header file install as those aren't in picolibc
generated by cgit v0.10.2-6-g49f6 at 2024-06-28 10:23:10 (GMT)