staging/pepe2k/toolchain/Config.in, branch v21.02.2Staging tree of Piotr Dymaczhttps://git.openwrt.org/openwrt/staging/pepe2k/atom?h=v21.02.22020-12-22T23:45:19Ztoolchain: Fix glibc selection on ARC targets2020-12-22T23:45:19ZHauke Mehrtens2020-12-22T23:32:41Zurn:sha1:920b692667470cf666ebb573f9213eccf3117702
Without this change no libc is selected and the build will fail. This
will select glibc for ARC CPUs.
Fixes: 95f1002acab5 ("toolchain: default to glibc for ARC")
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
toolchain: remove uClibc-ng config stuff2020-12-22T18:11:50ZRosen Penev2020-12-12T03:24:49Zurn:sha1:2207917acc7cd93db5b3bc9c6c5b898c38ec39aa
This is in preparation for removing it.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
toolchain: default to glibc for ARC2020-12-22T18:11:50ZRosen Penev2020-12-12T03:18:33Zurn:sha1:95f1002acab574c24ad78f4453f091bf5a6731c7
glibc 2.32 gained support for the ARC architecture.
This is preparation for removing uClibc-ng.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
toolchain: remove gcc libssp and use libc variant2020-06-17T21:57:07ZIan Cooper2020-06-15T21:14:04Zurn:sha1:b933f9cf0cb254e368027cad6d5799e45b237df5
Removes the standalone implementation of stack smashing protection
in gcc's libssp in favour of the native implementation available
in glibc and uclibc. Musl libc already uses its native ssp, so this
patch does not affect musl-based toolchains.
Stack smashing protection configuration options are now uniform
across all supported libc variants.
This also makes kernel-level stack smashing protection available
for x86_64 and i386 builds using non-musl libc.
Signed-off-by: Ian Cooper <iancooper@hotmail.com>
toolchain: Simplify libc selection2019-10-21T11:28:18ZRosen Penev2019-10-08T22:24:34Zurn:sha1:8f02ab1839306ec2cacbb3b2c86e28aa019ed0ff
uClibc-ng is only needed for ARC. Simplify the conditions.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
toolchain: Remove powerpc64 libc restriction2019-08-05T21:22:26ZRosen Penev2019-07-18T01:57:40Zurn:sha1:aa4f68ac9199fe20168dfd305cf5140f919bf0b3
Starting with version 1.1.15, musl supports powerpc64.
There are no known users of powerpc64 yet.
This is effectively a revert of 0de93311e1575ab6f8e9e90b5023b6fb2cedcf1f
Signed-off-by: Rosen Penev <rosenp@gmail.com>
toolchain: replace LEDE in help text2019-06-10T09:31:52ZKarl Pálsson2019-06-05T17:16:52Zurn:sha1:3b36aae9d5ec06d2e849212a70e3c8350a3b60b5
Use generic wording.
Signed-off-by: Karl Pálsson <karlp@etactica.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [fixed a -> á]
musl: improve crypt() size hack2019-01-22T11:08:03ZJo-Philipp Wich2019-01-22T08:50:09Zurn:sha1:ceb625439a84c7ea4ab1e39f126b6baffc48d1cd
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: Replace YASM with NASM2018-07-05T14:17:06ZTed Hess2018-06-28T23:28:02Zurn:sha1:0f543883cd0505a98fdc680ce2f08cbfca6d52a7
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>
toolchain: gdb: activate on ARM642018-02-10T19:15:52ZHauke Mehrtens2018-02-05T21:39:58Zurn:sha1:e387a1b4e4f57ec6e436990bca3de5de8d840d80
gdb supports ARM64 since quite some time now, activate it there like on
other CPU architectures.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>