aboutsummaryrefslogtreecommitdiffstats
path: root/toolchain
Commit message (Collapse)AuthorAgeFilesLines
* glibc: update to latest 2.27 commit [BZ #22964]Hans Dedecker2019-04-081-2/+2
| | | | | | de9d4aa353 ja_JP locale: Add entry for the new Japanese era [BZ #22964] Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* toolchain: ARM: Fix option conflict with multiarchBoris Krasnovskiy2019-03-251-0/+5
| | | | | | | | | | | | This problem exposed when compiling glibc, but applicable across the board. gcc compiles runtime libraries for all supported architectures, unless otherwise specified, and later selects applicable library based -m[arch,cpu,*] options, thus these options should not be passed to gcc as they break the compilation process. Signed-off-by: Boris Krasnovskiy <borkra@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [modified so it only touches ARM - I'm too chicken, changed authors email]
* toolchain: ARM: Fix toolchain compilation for gcc 8.xBoris Krasnovskiy2019-03-251-2/+6
| | | | | | | | | | | | | | | | | | | | | | | | Set the toolchain's ARM CPU and FPU architectures by utilizing' gcc's --with-cpu / --with-fpu configure options that: "Specify which cpu variant the compiler should generate code for by default. cpu will be used as the default value of the -mcpu= switch." This will resolve the following kernel compilation failures under gcc 8.x on ARM because the kernel wants to set (possibly conflicting) optimization flags. .../ccyVnmrs.s:204: Error: selected processor does not support `dmb ish' in ARM mode .../ccyVnmrs.s:215: Error: architectural extension `mp' is not allowed for the current base architecture .../ccyVnmrs.s:216: Error: selected processor does not support `pldw [r4]' in ARM mode Because this is a big change, the .config and toolchain need to be refreshed (as in removed and regenerated). Reported-by: Ansuel Smith <ansuelsmth@gmail.com> Reported-by: Daniel Engberg <daniel.engberg.lists@pyret.net> [#1203] Signed-off-by: Boris Krasnovskiy <borkra@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [extended commit message, removed now-deprecated CPU_CFLAGS, changed author to gmail address]
* glibc: update to latest 2.27 commitHans Dedecker2019-03-221-2/+2
| | | | | | 1ab314d8d3 S390: Mark vx and vxe as important hwcap. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* toolchain: Remove binutils 2.29 for ARC targetsDaniel Engberg2019-03-203-18/+0
| | | | | | Remove binutils 2.29 for ARC targets Signed-off-by: Daniel Engberg <daniel.engberg.lists@pyret.net>
* toolchain: Use binutils 2.32 by default for ARCDaniel Engberg2019-03-202-3/+2
| | | | | | Use binutils 2.32 by default for ARC targets Signed-off-by: Daniel Engberg <daniel.engberg.lists@pyret.net>
* toolchain: Remove GCC 7.1 for ARC targetsDaniel Engberg2019-03-2022-981/+0
| | | | | | Remove GCC 7.1 for ARC targets Signed-off-by: Daniel Engberg <daniel.engberg.lists@pyret.net>
* toolchain: Use GCC 8.3.0 by default for ARCDaniel Engberg2019-03-202-1/+2
| | | | | | | | Use GCC 8.3.0 by default for ARC targets Includes a fix by Evgeniy Didin which fixes GCC version selection if DEVEL isn't set Signed-off-by: Daniel Engberg <daniel.engberg.lists@pyret.net>
* toolchain/binutils: Add binutils 2.32Daniel Engberg2019-02-267-0/+110
| | | | | | Add binutils 2.32 to repo Signed-off-by: Daniel Engberg <daniel.engberg.lists@pyret.net>
* toolchain: Update to GCC 8.3.0Daniel Engberg2019-02-2622-7/+6
| | | | | | | | | Update GCC to 8.3.0 Refresh patches Allow GCC to be used for ARC Source: https://github.com/openwrt/openwrt/pull/1803#issuecomment-462334890 Signed-off-by: Daniel Engberg <daniel.engberg.lists@pyret.net>
* toolchain/gcc: Remove workaround for GCC 4.8Daniel Engberg2019-02-261-5/+2
| | | | | | GCC 4.8 was removed a long time ago... Signed-off-by: Daniel Engberg <daniel.engberg.lists@pyret.net>
* toolchain/binutils: Remove 2.30Daniel Engberg2019-02-178-222/+0
| | | | | | Remove binutils 2.30 Signed-off-by: Daniel Engberg <daniel.engberg.lists@pyret.net>
* glibc: update to latest 2.27 commit [BZ #24180]Hans Dedecker2019-02-091-2/+2
| | | | | | 9f44fa22cb Add compiler barriers around modifications of the robust mutex list for pthread_mutex_trylock. [BZ #24180] Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* toolchain/musl: update to version 1.1.21Christian Lamparter2019-02-053-7/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | <https://www.openwall.com/lists/musl/2019/01/21/8> "This release makes improvements with respect to default thread stack size, including increasing the default from 80k to 128k, increasing the default guard size from 4k to 8k, and allowing the default to be increased via ELF headers so that programs that need larger stacks can be build without source-level changes, using just LDFLAGS. Insufficient stack size for AIO threads on kernels that don't honor the constant MINSIGSTKSZ is also fixed. The glob core has been rewritten to fix inability to see past searchable-but-unreadable path components, and to avoid excessive stack usage and unnecessary syscalls. The tsearch AVL tree implementation has also been rewritten for better size and performance. The math library adds more native single-instruction implementations for arm, s390x, powerpc, and x86_64. Various bugs are fixed, including several possible deadlocks, one of which was a new regression in 1.1.20." detailed release notes can be found in the WHATSNEW file: <http://git.musl-libc.org/cgit/musl/tree/WHATSNEW#n1989> Tested-by: Koen Vandeputte <koen.vandeputte@ncentric.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* glibc: update to latest 2.27 commit (BZ #24155,BZ #24097)Hans Dedecker2019-02-041-2/+2
| | | | | | | | | | | | | | 2ebadb6451 x86-64 memcmp: Use unsigned Jcc instructions on size [BZ #24155] 3a5ae8db68 x86-64 strnlen/wcsnlen: Properly handle the length parameter [BZ #24097] 2c016ffa24 x86-64 strncpy: Properly handle the length parameter [BZ #24097] d8457edece x86-64 strncmp family: Properly handle the length parameter [BZ #24097] 55f8812858 x86-64 memset/wmemset: Properly handle the length parameter [BZ #24097] efc3714845 x86-64 memrchr: Properly handle the length parameter [BZ #24097] a4690969ed x86-64 memcpy: Properly handle the length parameter [BZ #24097] 6465327195 x86-64 memcmp/wmemcmp: Properly handle the length parameter [BZ #24097] 50117e00a1 x86-64 memchr/wmemchr: Properly handle the length parameter [BZ #24097] Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* toolchain/gcc: backport FORTIFY patch to 5.5.0Hans Dedecker2019-02-041-0/+1092
| | | | | | | | | | | | Commit e61061a0886e2d0d6b075d75ae9b53d0a6bc9042 added support for hardening options in the toolchain. However this breaks the gcc5.5.0 compilation in case FORTIFY_SOURCE is set different from FORTIFY_SOURCE_NONE as reported in [1]. Fix this by backporting the upstream patch which fixes this in later gcc versions [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?format=multiple&id=61164 Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* update uClibc-ng from 1.0.30 to 1.0.31protonesso2019-01-271-2/+2
| | | | Signed-off-by: protonesso <nagakamira@gmail.com>
* musl: improve crypt() size hackJo-Philipp Wich2019-01-224-25/+54
| | | | | | | | | | | | | | Instead of silently downgrading any non-MD5 crypt() request to DES, cleanly fail with return NULL and errno = ENOSYS. This allows callers to notice the missing support instead of the unwanted silent fallback to DES. Also add a menuconfig toolchain option to optionally disable the crypt size hack completely. This can be probably made dependant on SMALL_FLASH or a similar feature indicator in a future commit. Ref: https://github.com/openwrt/openwrt/pull/1331 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* toolchain/gdb: bump to 8.2.1Koen Vandeputte2019-01-071-2/+2
| | | | | | | | | | | | | | | | PR build/23516 (gdb build error under msys+mingw: strip can't handle gdb-add-index.exe) PR build/23623 (install-strip fails) PR rust/23626 (gdb crashes in upstream rust nil-enum test) PR rust/23650 (rust field name access error mentions "foo") PR gdb/23663 (gdb 8.1.1: undefined rpl_stat function with musl toolchains) PR python/23669 (gdb.execute("show commands") doesn't work) PR python/23714 (Command repetition stops working after gdb.execute) PR gdb/23838 (8.2 regression for invalid -data-directory) PR gdb/23974 ("info os" crash when specifying invalid object) PR gdb/23999 (SYMBOL_LANGUAGE assertion failure on AIX) PR gdb/24003 (Error when binary searching CUs for a specific DIE when using DWZ) Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* glibc: update to latest 2.27 commit (BZ #24018)Hans Dedecker2019-01-071-2/+2
| | | | | | | 68c2930a56 NEWS: add entries for bugs 23275, 23861, and 23907 766e8fb932 intl: Do not return NULL on asprintf failure in gettext [BZ #24018] Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* glibc: update to latest 2.27 commit (BZ #24027, BZ #23927)Hans Dedecker2019-01-011-2/+2
| | | | | | | | | | | | | | | | 3981fc3453 malloc: Always call memcpy in _int_realloc [BZ #24027] f6d0e8c36f Fix rwlock stall with PREFER_WRITER_NONRECURSIVE_NP (bug 23861) 2794474c65 powerpc: Add missing CFI register information (bug #23614) d8ca7a0c71 Fix _dl_profile_fixup data-dependency issue (Bug 23690) f1e211096b inet/tst-if_index-long: New test case for CVE-2018-19591 [BZ #23927] 4e9f34e54f support: Implement <support/descriptors.h> to track file descriptors e75481a7a7 support: Close original descriptors in support_capture_subprocess 0f79dc0be3 support_quote_string: Do not use str parameter name 6b2dd53aa0 support: Implement support_quote_string 50477165b9 malloc: Add another test for tcache double free check. 4b246928bd malloc: tcache double free check Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* gcc: update to version 7.4.0Hauke Mehrtens2018-12-1526-322/+8
| | | | | | | | This updates the GCC to the next minor release which fixes 178 bugs. The two removed patches are included in gcc 7.4.0 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Tested-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* glibc: update to latest 2.27 commit (BZ #23927)Hans Dedecker2018-12-141-2/+2
| | | | | | | | | | | | | | | f6d0e8c36f Fix rwlock stall with PREFER_WRITER_NONRECURSIVE_NP (bug 23861) 2794474c65 powerpc: Add missing CFI register information (bug #23614) d8ca7a0c71 Fix _dl_profile_fixup data-dependency issue (Bug 23690) f1e211096b inet/tst-if_index-long: New test case for CVE-2018-19591 [BZ #23927] 4e9f34e54f support: Implement <support/descriptors.h> to track file descriptors e75481a7a7 support: Close original descriptors in support_capture_subprocess 0f79dc0be3 support_quote_string: Do not use str parameter name 6b2dd53aa0 support: Implement support_quote_string 50477165b9 malloc: Add another test for tcache double free check. 4b246928bd malloc: tcache double free check Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* glibc: update to latest 2.27 commit (BZ #23927)Hans Dedecker2018-12-061-2/+2
| | | | | | 9f433fc791 CVE-2018-19591: if_nametoindex: Fix descriptor for overlong name [BZ #23927] Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* glibc: update to latest 2.27 commitHans Dedecker2018-11-221-2/+2
| | | | | | | 1517dfb8aa Add an additional test to resolv/tst-resolv-network.c 1050634904 libanl: properly cleanup if first helper thread creation failed (bug 22927) Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* glibc: update to latest 2.27 commit (BZ#23709,BZ#23822)Hans Dedecker2018-11-051-2/+2
| | | | | | | | d8eee5ef55 x86: Fix Haswell CPU string flags (BZ#23709) 5cd5309d91 i64: fix missing exp2f, log2f and powf symbols in libm.a [BZ #23822] 1759ea197b conform: XFAIL siginfo_t si_band test on sparc64 Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* glibc: update to latest 2.27 commit (BZ #23562, BZ #23275)Hans Dedecker2018-10-231-2/+2
| | | | | | | 77b4b8231e signal: Use correct type for si_band in siginfo_t [BZ #23562] 5bdb6897fc Fix race in pthread_mutex_lock while promoting to PTHREAD_MUTEX_ELISION_NP [BZ #23275] Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* toolchain/musl: Don't override optimization set by upstreamDaniel Engberg2018-10-201-2/+5
| | | | | | | | | | Don't override optimization set by upstream. Provides a speed increase for internal (library), malloc and string operations in musl. Signed-off-by: Daniel Engberg <daniel.engberg.lists@pyret.net> [add : to PKG_RELEASE release variable for consistency] Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* toolchain/glibc: update to 2.27+Hans Dedecker2018-10-162-4/+4
| | | | Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* binutils: Use 2.31.1 by defaultDaniel Engberg2018-10-072-2/+2
| | | | | | Set binutils 2.31.1 as default Signed-off-by: Daniel Engberg <daniel.engberg.lists@pyret.net>
* toolchain/binutils: Fix u-boot on some armhf platformsDaniel Engberg2018-10-071-0/+276
| | | | | | | | | | Backport commit 3d9c8f6b3f033a6092425b7344647fb51dbed5c6 Without this binutils doesn't properly link u-boot Source: https://sourceware.org/bugzilla/show_bug.cgi?id=23571 Signed-off-by: Daniel Engberg <daniel.engberg.lists@pyret.net>
* toolchain/fortify-headers: Update to 1.0Daniel Engberg2018-10-071-2/+2
| | | | | | Update fortify-headers to 1.0 Signed-off-by: Daniel Engberg <daniel.engberg.lists@pyret.net>
* build: drop buildbot toolchain rebuild check when not using gitFelix Fietkau2018-09-241-0/+2
| | | | | | | | The check cleans and rebuilds the toolchain if it changed on update. When building from a source tarball, it is reasonable to expect that there will be no updates, so no rebuild check is necessary Signed-off-by: Felix Fietkau <nbd@nbd.name>
* toolchain/musl: update to version 1.1.20Christian Lamparter2018-09-216-88/+32
| | | | | | | | | | | | | | | | | | | | | | | This release introduces the ability to replace/interpose the allocator (malloc) subject to certain restrictions, adds an experimental m68k port, and makes notable improvements to stdio (application-provided buffers), getaddrinfo (AI_ADDRCONFIG, support for IPv4-only kernel configurations), the dynamic linker (safety against dlopen of libraries using initial-exec TLS model, reclaiming unused memory on FDPIC archs, better dladdr results), and handling of default thread stack size (pthread_setattr_default_np now works more reliably). Many bugs have been fixed, including potentially dangerous regressions in iconv (only for new conversions to legacy encodings) and visibly incorrect behavior in printf on non-x86 archs (%a format with precision specifier), in getopt_long_only when short options are a prefix for a long option, in complex arc-trig/hyperbolic functions, in strftime and mktime (timezone-specific issues), and numerous less-obvious places. Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [altered commit msg a bit keeping it tight] Tested-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* toolchain/glibc: update to latest 2.26 commitHans Dedecker2018-09-131-2/+2
| | | | | | | c5c90b480e Fix segfault in maybe_script_execute. 174709d879 pthread_cond_broadcast: Fix waiters-after-spinning case [BZ #23538] Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* toolchain/gdb: bump to 8.2Koen Vandeputte2018-09-073-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | *** Changes in GDB 8.2 Support for the following target has been added: RiscV ELF (riscv*-*-elf) Support for following targets and native configurations has been removed: m88k running OpenBSD (m88*-*-openbsd*) SH-5/SH64 ELF (sh64-*-elf*) SH-5/SH64 (sh*) SH-5/SH64 running GNU/Linux (sh*-*-linux*) SH-5/SH64 running OpenBSD (sh*-*-openbsd*) Various Python API enhancements Aarch64/Linux enhancements: SVE support. Hardware watchpoints improvements for entities stored at unaligned addresses. New "c" response to disable the pager for the rest of the current command. C expressions can now use _Alignof, and C++ expressions can now use alignof. Improved flexibility for loading symbol files. The 'info proc' command nows works on running processes on FreeBSD systems as well as core files created on FreeBSD systems. A new --enable-codesign=CERT configure option to automatically codesign GDB after build (useful on MacOS X). Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* toolchain/gcc: update 8.x to 8.2.0Syrone Wong2018-08-2021-8/+8
| | | | | | This release fixes LTO link-time performance problems and C++ bug introduced in GCC 8.1 Signed-off-by: Syrone Wong <wong.syrone@gmail.com>
* toolchain/gcc: add config symbol to determine how to apply path remappingSyrone Wong2018-08-201-0/+5
| | | | | | | | | Added boolean symbol for GCC 8 and higher, when we add newer GCC, we don't have to modify rules.mk to keep things consistant. Fixes: da9d760 ("rules.mk: replace iremap when using GCC 8") Signed-off-by: Syrone Wong <wong.syrone@gmail.com>
* toolchain/glibc: update to latest 2.26 commitHans Dedecker2018-08-071-2/+2
| | | | | | | | | | | | | c9570bd2f5 x86: Populate COMMON_CPUID_INDEX_80000001 for Intel CPUs [BZ #23459] 86e0996b1a x86: Correct index_cpu_LZCNT [BZ #23456] cf6deb084b conform/conformtest.pl: Escape literal braces in regular expressions b12bed3e06 stdio-common/tst-printf.c: Remove part under a non-free license [BZ #23363] 20dc7a909a libio: Add tst-vtables, tst-vtables-interposed 4b10e69b1f Synchronize support/ infrastructure with master 762e9d63d5 NEWS: Reorder out-of-order bugs 2781bd5a86 libio: Disable vtable validation in case of interposition [BZ #23313] Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* toolchain/gdb: bump to 8.1.1Koen Vandeputte2018-08-013-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | GDB 8.1.1 brings the following fixes and enhancements over GDB 8.1: * PR gdb/22824 (misleading description of new rbreak Python function in GDB 8.1 NEWS file) * PR gdb/22849 (ctrl-c doesn't work in extended-remote) * PR gdb/22907 ([Regression] gdbserver doesn't work with filename-only binaries) * PR gdb/23028 (inconsistent disassemble of vcvtpd2dq) * PR gdb/23053 (Fix -D_GLIBCXX_DEBUG gdb-add-index regression) * PR gdb/23127 ([AArch64] GDB cannot be used for debugging software that uses high Virtual Addresses) * PR server/23158 (gdbserver no longer functional on Windows) * PR breakpoints/23210 ([8.1/8.2 Regression] Bogus Breakpoint address adjusted from 0xf7fe7dd3 to 0xfffffffff7fe7dd3) GDB 8.1 includes the following changes and enhancements: * Breakpoints on C++ functions are now set on all scopes by default ("wild" matching); * Support for inserting breakpoints on functions marked with C++ ABI tags; * Target floating-point arithmetic emulation during expression evaluation (requires MPFR 3.1 or later); * Various Python Scripting enhancements; * Improved Rust support; in particular, Trait objects can now be inspected when debugging Rust code; * GDB no longer makes assumptions about the type of symbols without debugging information to avoid producing erroneous and often confusing results; * The 'enable' and 'disable' commands now accept a range of breakpoint locations; * New 'starti' command to start the program at the first instruction; * New 'rbreak' command to insert a number of breakpoints via a regular expression pattern (requires Python); * The 'ptype' command now supports printing the offset and size of the fields in a struct; * The 'gcore' command now supports dumping all the memory mappings ('-a' command-line option); * New shortcuts for TUI Single-Key mode: 'i' for stepi, and 'o' for nexti; * GDBserver enhancements: ** Support for transmitting environment variables to GDBserver; ** Support for starting inferior processes with a specified initial working directory; ** On Unix systems, support for globbing expansion and variable substitution of inferior command-line arguments; * Various completion enhancements; * The command used to compile and inject code with the 'compile' command is now configurable; * New '--readnever' command-line option to speed the GDB startup when debugging information is not needed; * Support for the following new native configurations: ** FreeBSD/aarch64 (aarch64*-*-freebsd*); ** FreeBSD/arm (arm*-*-freebsd*); * Support for the following new targets: ** FreeBSD/aarch64 (aarch64*-*-freebsd*); ** FreeBSD/arm (arm*-*-freebsd*); ** OpenRISC ELF (or1k*-*-elf) * Removed support for the following targets and native configurations: ** Solaris2/x86 (i?86-*-solaris2.[0-9]); ** Solaris2/sparc (sparc*-*-solaris2.[0-9]); Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* toolchain/binutils: Add binutils 2.31.1Daniel Engberg2018-07-307-0/+110
| | | | | | Add binutils 2.31.1 to repo Signed-off-by: Daniel Engberg <daniel.engberg.lists@pyret.net>
* toolchain/gcc: add GCC 8.1.0Syrone Wong2018-07-2222-0/+862
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Changes compared to GCC 7.x 001-revert_register_mode_search.patch dropped The underlying issue is described at the end of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58139 It is fixed by the upstream commit: https://github.com/gcc-mirror/gcc/commit/3fa2798aa887d141d86985240f03e2f3809e7e62 020-PR-libstdc-81797-Add-.NOTPARALLEL-to-include-Makefil.patch dropped due to already upstream 100-PR-rtl-optimization-83496.patch dropped due to already upstream 910-mbsd_multi.patch modified to fix ambiguous overloaded inform() call error gcc/input.h header: define UNKNOWN_LOCATION ((source_location) 0) - inform (0, "someone does not honour COPTS correctly, passed %d times", - honour_copts); + inform (UNKNOWN_LOCATION, "someone does not honour COPTS correctly, passed %d times", + honour_copts); 940-no-clobber-stamp-bits.patch dropped due to fixed upstream by another way upstream commit: https://github.com/gcc-mirror/gcc/commit/87b2d547f8ac9778d66909b8726fe967d1efbc74 950-cpp_file_path_translation.patch dropped, Both -fmacro-prefix-map and -ffile-prefix-map are added to gcc 8.1.0, if I understand it correctly, we should use -fmacro-prefix-map usage: -fmacro-prefix-map=@var{old}=@var{new} upstream commit: https://github.com/gcc-mirror/gcc/commit/859b51f83662d01e4f158ea9327db9ca37fe70b3 -iremap exists as a flag for a long time, for backward compatibility, I think we should keep the variable name unchanged but change its value in rules.mk for gcc 8.x and higher. Compile and run tested on x86_64 Signed-off-by: Syrone Wong <wong.syrone@gmail.com>
* binutils: remove version 2.27Felix Fietkau2018-07-108-147/+0
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* binutils: update to version 2.30, resolves issues with LTOFelix Fietkau2018-07-102-2/+2
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* binutils: backport an upstream fix for a linker bug that triggers with LTOFelix Fietkau2018-07-101-0/+112
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* nasm: disable LTO, remove host specific workaroundsFelix Fietkau2018-07-101-7/+1
| | | | | | | | | | | | The recent build failures on various platforms were apparently caused by the fact that LTO build support in the configure script does not check if it has a suitable version of gcc and simply assumes that gcc-ar is available and can be used for intermediate files. Since we really don't need to build nasm with LTO, simply disable it and keep the whole build more portable Signed-off-by: Felix Fietkau <nbd@nbd.name>
* toolchain/nasm: force ar and ranlib only on macOSXHauke Mehrtens2018-07-081-3/+5
| | | | | | | | | | On Debian 9 nasm does not build when we force it to use ranlib, for macOSX this is needed. Only force this on macOSX and not on any other OS, this should fix the build of nasm on Linux systems. On my Debian system the nasm configure script selects gcc-ranlib and gcc-ar instead. Fixes: d3a7587eb95 ("toolchain/nasm: fix missing AR/RANLIB variables") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* toolchain/nasm: Backport GCC8 compatibility fix from upstream repoTed Hess2018-07-071-0/+15
| | | | Signed-off-by: Ted Hess <thess@kitschensync.net>
* toolchain/nasm: fix missing AR/RANLIB variablesFelix Fietkau2018-07-071-4/+5
| | | | | | Fixes build on macOS Signed-off-by: Felix Fietkau <nbd@nbd.name>
* toolchain: Replace YASM with NASMTed Hess2018-07-053-20/+13
| | | | | | | | | | Packages libx264 and ffmpeg are built with ASM options on x86 platforms. The current libx264 version no longer builds with YASM and requires NASM. ffmpeg 3.x can be built with either YASM or NASM however, furture 4.x versions will require NASM. Signed-off-by: Ted Hess <thess@kitschensync.net> Acked-by: Rosen Penev <rosenp@gmail.com>