NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
c2caf816e9
kumquat-buildroot/package/binutils/Config.in.host

60 lines
1.5 KiB
Plaintext
Raw Normal View History

Add some seperators
2004-10-09 07:33:05 +02:00
comment "Binutils Options"
toolchain: disable SSP support if CFI support in binutils is missing As reported by [1], SSP support is missing in the Buildroot toolchain for microblaze even if it's requested by selecting BR2_TOOLCHAIN_HAS_SSP config option. In Buildroot, we are using libssp provided by the C library (glibc, musl, uClibc-ng) when available. We are not using libssp from gcc. So for a microblaze glibc based toolchain, the SSP support is enabled unconditionally by a select BR2_TOOLCHAIN_HAS_SSP. BR2_microblazeel=y BR2_TOOLCHAIN_BUILDROOT_GLIBC=y BR2_KERNEL_HEADERS_4_14=y BR2_BINUTILS_VERSION_2_30_X=y BR2_GCC_VERSION_8_X=y BR2_TOOLCHAIN_BUILDROOT_CXX=y While building the toolchain, we are building host-binutils which provide "as" (assembler) and host-gcc-initial wich provide a minimal cross gcc (C only cross-compiler without any C library). When SSP support is requested, gcc_cv_libc_provides_ssp=yes is added to the make command line (see [2] for full details) With this setting, the SSP support is requested but it's not available in the end and the toochain build succeed. When the microblaze toolchain is imported to Biuldroot (2018.05) as external toolchain with BR2_TOOLCHAIN_EXTERNAL_HAS_SSP set, the build stop with : "SSP support not available in this toolchain, please disable BR2_TOOLCHAIN_EXTERNAL_HAS_SSP" The test is doing the following command line: echo 'void main(){}' | [...]/host/bin/microblazeel-linux-gcc.br_real -Werror -fstack-protector -x c - -o [...]/build/.br-toolchain-test.tmp cc1: error: -fstack-protector not supported for this target [-Werror] When we look at the gcc-final log file (config.log) we can see this error several time when using the minimal gcc (from host-gcc-initial). So Why the minimal gcc doesn't support SSP? When we look at the gcc-initial log file (config.log) we can see an error with 'as': configure:23194: checking assembler for cfi directives configure:23209: [...]microblazeel-buildroot-linux-gnu/bin/as -o conftest.o conftest.s >&5 conftest.s: Assembler messages: conftest.s:2: Error: CFI is not supported for this target conftest.s:3: Error: CFI is not supported for this target conftest.s:4: Error: CFI is not supported for this target conftest.s:5: Error: CFI is not supported for this target conftest.s:6: Error: CFI is not supported for this target conftest.s:7: Error: CFI is not supported for this target configure:23212: $? = 1 configure: failed program was .text .cfi_startproc .cfi_offset 0, 0 .cfi_same_value 1 .cfi_def_cfa 1, 2 .cfi_escape 1, 2, 3, 4, 5 .cfi_endproc This is the only relevant difference compared to a nios2 toolchain where libssp is enabled and available (nios2 is an example). "CFI" stand for "Control Flow Integrity" and it seems that SSP support requires CFI target support (see [3] for some explanation). The SSP support seems to depends on CFI support, but the toolchain infrastructure is not detailed enough to handle the CFI dependency. The NiosII toolchains built with binutils < 2.30 are also affected by this issue. This patch improve the toolchain infrastructure by adding a new BR2_PACKAGE_HOST_BINUTILS_SUPPORTS_CFI blind option Disable SSP support for microblaze entirely. Disable SSP support for nios2 only with Binutils < 2.30. Fixes: https://gitlab.com/free-electrons/toolchains-builder/-/jobs/72006389 [1] https://gitlab.com/free-electrons/toolchains-builder/issues/1 [2] https://git.buildroot.net/buildroot/tree/package/gcc/gcc.mk?h=2018.05#n275 [3] https://grsecurity.net/rap_faq.php Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> [Thomas: adjust how the BR2_PACKAGE_HOST_BINUTILS_SUPPORTS_CFI option is expressed.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-09-08 16:41:39 +02:00
config BR2_PACKAGE_HOST_BINUTILS_SUPPORTS_CFI
bool
default y
depends on !BR2_microblaze
Major buildroot facelift, step one. -Erik
2004-10-09 03:06:03 +02:00
choice
prompt "Binutils Version"
package/binutils: switch to use 2.33.1 as the default version Now that binutils 2.34 has been released, it is time to move to binutils 2.33.1 as the default binutils version, instead of 2.32. Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-06-25 14:13:01 +02:00
default BR2_BINUTILS_VERSION_2_33_X if !BR2_arc && !BR2_csky
binutils: allow the selection of upstream binutils 2.29 for ARC As of today quite a lot of ARC stuff got merged in upsream such that we may finally use upstream realease for building and even running Linux kernel and rootfs built with vanilla binutils. Essentially upstream release is still a bit behind our GitHub-based releases but let's try to use vanilla version and if we're lucky enough with just a small set of back-ported patches we'll be able to use vanilla release(s) for everything in Buildroot. Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com> Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Peter Korsgaard <peter@korsgaard.com> [Thomas: fixup the condition to select the special binutils site for ARC.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-11-10 17:37:26 +01:00
default BR2_BINUTILS_VERSION_ARC if BR2_arc
package/binutils: add C-SKY specific version Signed-off-by: Guo Ren <ren_guo@c-sky.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-05-31 08:39:03 +02:00
default BR2_BINUTILS_VERSION_CSKY if BR2_csky
Major buildroot facelift, step one. -Erik
2004-10-09 03:06:03 +02:00
help
Select the version of binutils you wish to use.
package/binutils: add support for binutils 2.32 Remove upstream ARC and Xtensa patches. Keep all other patches from binutils 2.31.1. See the release note: https://sourceware.org/ml/binutils/2019-02/msg00010.html While testing the Binutils 2.32 version bump, the Qemu xtensa defconfig (that was using a kernel 4.16) needed to be updated with a patch [1] from kernel 4.19 otherwise the kernel doesn't boot with binutils 2.32 [2]. Since then, all Qemu defconfig has been updated by commit [3] to use a 4.19 kernel, so the issue no longer exists. All other architectures has been tested using toolchain-builder [4]. [1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4119ba211bc4f1bf638f41e50b7a0f329f58aa16 [2] https://www.sourceware.org/ml/binutils/2019-02/msg00015.html [3] fd8a02fd75d652b85f64c1cd7e9adf1ee2329261 [4] https://gitlab.com/kubu93/toolchains-builder/pipelines/45896638 Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-03-10 11:44:28 +01:00
config BR2_BINUTILS_VERSION_2_32_X
bool "binutils 2.32"
package/binutils: add C-SKY specific version Signed-off-by: Guo Ren <ren_guo@c-sky.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-05-31 08:39:03 +02:00
depends on !BR2_csky
package/binutils: add support for binutils 2.32 Remove upstream ARC and Xtensa patches. Keep all other patches from binutils 2.31.1. See the release note: https://sourceware.org/ml/binutils/2019-02/msg00010.html While testing the Binutils 2.32 version bump, the Qemu xtensa defconfig (that was using a kernel 4.16) needed to be updated with a patch [1] from kernel 4.19 otherwise the kernel doesn't boot with binutils 2.32 [2]. Since then, all Qemu defconfig has been updated by commit [3] to use a 4.19 kernel, so the issue no longer exists. All other architectures has been tested using toolchain-builder [4]. [1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4119ba211bc4f1bf638f41e50b7a0f329f58aa16 [2] https://www.sourceware.org/ml/binutils/2019-02/msg00015.html [3] fd8a02fd75d652b85f64c1cd7e9adf1ee2329261 [4] https://gitlab.com/kubu93/toolchains-builder/pipelines/45896638 Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-03-10 11:44:28 +01:00
package/binutils: add binutils 2.33.1 Keep sh-conf and poison-system-directories patches. Remove xtensa patches already in this version [1] [2] [3]. Revert an upstream patch since it prevent booting a sh4 system under Qemu as reported on the Binutils mailing list [5] [6]. This commit is not related to sh4, it's weird that it is the only affected architecture. [1] https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=2487ef07c28b961c6e2b8c51161f88f93b181d07 [2] https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=403b0b61f6d4358aee8493cb1d11814e368942c9 [3] https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=548791769dc737f05cb12e5ee4190b7e853beac9 [4] https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=ebd2263ba9a9124d93bbc0ece63d7e0fae89b40e [5] https://sourceware.org/ml/binutils/2019-10/msg00105.html [6] https://sourceware.org/ml/binutils/2019-11/msg00407.html See: https://www.sourceware.org/ml/binutils/2019-10/msg00103.html Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Max Filippov <jcmvbkbc@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-11-30 16:17:50 +01:00
config BR2_BINUTILS_VERSION_2_33_X
bool "binutils 2.33.1"
depends on !BR2_csky
package/binutils: disable binutils >= 2.33.1 for configurations using BR2_BINFMT_FLAT The patch added by [1] to fix a segfault with elf2flt when binutils 2.33.1 is used on ARM, introduce a regression with previous binutils version on m68k and ARM. Theses issues has been reported upstreme [2] [3]. For now, disable binutils >= 2.33.1 for configurations using BR2_BINFMT_FLAT. [1] 2b064f86b6a0fd683f307b51f12d9d919fcaa386 [2] https://github.com/uclinux-dev/elf2flt/pull/16 [3] https://github.com/uclinux-dev/elf2flt/issues/12 Signed-off-by: Romain Naour <romain.naour@smile.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2020-02-27 23:19:21 +01:00
# https://github.com/uclinux-dev/elf2flt/pull/16
# https://github.com/uclinux-dev/elf2flt/issues/12
depends on !BR2_BINFMT_FLAT
package/binutils: add binutils 2.33.1 Keep sh-conf and poison-system-directories patches. Remove xtensa patches already in this version [1] [2] [3]. Revert an upstream patch since it prevent booting a sh4 system under Qemu as reported on the Binutils mailing list [5] [6]. This commit is not related to sh4, it's weird that it is the only affected architecture. [1] https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=2487ef07c28b961c6e2b8c51161f88f93b181d07 [2] https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=403b0b61f6d4358aee8493cb1d11814e368942c9 [3] https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=548791769dc737f05cb12e5ee4190b7e853beac9 [4] https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=ebd2263ba9a9124d93bbc0ece63d7e0fae89b40e [5] https://sourceware.org/ml/binutils/2019-10/msg00105.html [6] https://sourceware.org/ml/binutils/2019-11/msg00407.html See: https://www.sourceware.org/ml/binutils/2019-10/msg00103.html Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Max Filippov <jcmvbkbc@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-11-30 16:17:50 +01:00
package/binutils: add version 2.34 Rebase existing patches. Keep BR2_BINFMT_FLAT disabled for binutils 2.34 since elf2flt issue is not fixed [1] [2]. [1] https://github.com/uclinux-dev/elf2flt/pull/16 [2] https://github.com/uclinux-dev/elf2flt/issues/12 See announce: https://lists.gnu.org/archive/html/info-gnu/2020-02/msg00000.html Signed-off-by: Romain Naour <romain.naour@smile.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-06-25 14:13:00 +02:00
config BR2_BINUTILS_VERSION_2_34_X
bool "binutils 2.34"
depends on !BR2_csky
# https://github.com/uclinux-dev/elf2flt/pull/16
# https://github.com/uclinux-dev/elf2flt/issues/12
depends on !BR2_BINFMT_FLAT
binutils: allow the selection of upstream binutils 2.29 for ARC As of today quite a lot of ARC stuff got merged in upsream such that we may finally use upstream realease for building and even running Linux kernel and rootfs built with vanilla binutils. Essentially upstream release is still a bit behind our GitHub-based releases but let's try to use vanilla version and if we're lucky enough with just a small set of back-ported patches we'll be able to use vanilla release(s) for everything in Buildroot. Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com> Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Peter Korsgaard <peter@korsgaard.com> [Thomas: fixup the condition to select the special binutils site for ARC.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-11-10 17:37:26 +01:00
config BR2_BINUTILS_VERSION_ARC
toolchain: Bump ARC tools to arc-2018.09-rc1 This commit bumps ARC toolchain to arc-2018.09-rc1. We want to test how new toolchain-rc1 builds packages, so we can make fixes before release of toolcain. ARC GNU tools of version arc-2018.09-rc1 bring some quite significant changes like: * Binutils v2.31.1 with additional ARC patches * GCC 8.2.1 with additional ARC patches * glibc 2.28 with additional ARC patches Please note that it is a release candidate and it might contain some breakages, please don't use it for production builds. Signed-off-by: Evgeniy Didin <didin@synopsys.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: arc-buildroot@synopsys.com Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-11-08 12:32:07 +01:00
bool "binutils arc (2.31)"
binutils: allow the selection of upstream binutils 2.29 for ARC As of today quite a lot of ARC stuff got merged in upsream such that we may finally use upstream realease for building and even running Linux kernel and rootfs built with vanilla binutils. Essentially upstream release is still a bit behind our GitHub-based releases but let's try to use vanilla version and if we're lucky enough with just a small set of back-ported patches we'll be able to use vanilla release(s) for everything in Buildroot. Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com> Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Peter Korsgaard <peter@korsgaard.com> [Thomas: fixup the condition to select the special binutils site for ARC.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-11-10 17:37:26 +01:00
depends on BR2_arc
package/binutils: add C-SKY specific version Signed-off-by: Guo Ren <ren_guo@c-sky.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-05-31 08:39:03 +02:00
config BR2_BINUTILS_VERSION_CSKY
bool "binutils csky"
depends on BR2_csky
Major buildroot facelift, step one. -Erik
2004-10-09 03:06:03 +02:00
endchoice
config BR2_BINUTILS_VERSION
string
toolchain: update ARC tools to arc-2020.03-release This commit bumps ARC toolchain to arc-2020.03-release. ARC GNU tools of version arc-2020.03-release bring some quite significant changes like: * Binutils 2.34 with additional ARC patches * GCC 9.3 with additional ARC patches * glibc 2.30 with additional ARC patches * GDB 10-prerelease with additional ARC patches Signed-off-by: Evgeniy Didin <Evgeniy.Didin@synopsys.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: arc-buildroot@synopsys.com Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-05-25 22:15:23 +02:00
default "arc-2020.03-release" if BR2_BINUTILS_VERSION_ARC
package/binutils: add C-SKY specific version Signed-off-by: Guo Ren <ren_guo@c-sky.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-05-31 08:39:03 +02:00
default "c66d8bbcebfddf713b2b436e1b135e6b125a55a5" if BR2_BINUTILS_VERSION_CSKY
package/binutils: add support for binutils 2.32 Remove upstream ARC and Xtensa patches. Keep all other patches from binutils 2.31.1. See the release note: https://sourceware.org/ml/binutils/2019-02/msg00010.html While testing the Binutils 2.32 version bump, the Qemu xtensa defconfig (that was using a kernel 4.16) needed to be updated with a patch [1] from kernel 4.19 otherwise the kernel doesn't boot with binutils 2.32 [2]. Since then, all Qemu defconfig has been updated by commit [3] to use a 4.19 kernel, so the issue no longer exists. All other architectures has been tested using toolchain-builder [4]. [1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4119ba211bc4f1bf638f41e50b7a0f329f58aa16 [2] https://www.sourceware.org/ml/binutils/2019-02/msg00015.html [3] fd8a02fd75d652b85f64c1cd7e9adf1ee2329261 [4] https://gitlab.com/kubu93/toolchains-builder/pipelines/45896638 Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-03-10 11:44:28 +01:00
default "2.32" if BR2_BINUTILS_VERSION_2_32_X
package/binutils: add binutils 2.33.1 Keep sh-conf and poison-system-directories patches. Remove xtensa patches already in this version [1] [2] [3]. Revert an upstream patch since it prevent booting a sh4 system under Qemu as reported on the Binutils mailing list [5] [6]. This commit is not related to sh4, it's weird that it is the only affected architecture. [1] https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=2487ef07c28b961c6e2b8c51161f88f93b181d07 [2] https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=403b0b61f6d4358aee8493cb1d11814e368942c9 [3] https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=548791769dc737f05cb12e5ee4190b7e853beac9 [4] https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=ebd2263ba9a9124d93bbc0ece63d7e0fae89b40e [5] https://sourceware.org/ml/binutils/2019-10/msg00105.html [6] https://sourceware.org/ml/binutils/2019-11/msg00407.html See: https://www.sourceware.org/ml/binutils/2019-10/msg00103.html Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Max Filippov <jcmvbkbc@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-11-30 16:17:50 +01:00
default "2.33.1" if BR2_BINUTILS_VERSION_2_33_X
package/binutils: add version 2.34 Rebase existing patches. Keep BR2_BINFMT_FLAT disabled for binutils 2.34 since elf2flt issue is not fixed [1] [2]. [1] https://github.com/uclinux-dev/elf2flt/pull/16 [2] https://github.com/uclinux-dev/elf2flt/issues/12 See announce: https://lists.gnu.org/archive/html/info-gnu/2020-02/msg00000.html Signed-off-by: Romain Naour <romain.naour@smile.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-06-25 14:13:00 +02:00
default "2.34" if BR2_BINUTILS_VERSION_2_34_X
- make sure we use the proper CC for building binutils. - add config option BR2_EXTRA_BINUTILS_CONFIG_OPTIONS for passing additional flags to binutils configure.
2006-03-10 09:46:36 +01:00
toolchain: add link-time-optimization support Add a new option BR2_GCC_ENABLE_LTO that builds gcc and binutils with LTO support. Individual packages still have to enable LTO explicitly by passing '-flto' to GCC, which passes it on to the linker. This option does not add that flag globally. Some packages detect if the compiler supports LTO and enable the flag if it does. To support LTO, ar and ranlib must be called with an argument which triggers the usage of the LTO plugin. Since GCC doesn't call these tools itself, it instead provides wrappers for ar and ranlib that pass the LTO arguments. This way existing Makefiles don't need to be changed for LTO support. However, these wrappers are called <tuple>-gcc-ar which matches the pattern to link to the buildroot wrapper in the external toolchain logic. So the external toolchain logic is updated to provide the correct symlink. [Thomas: - Add a separate BR2_BINUTILS_ENABLE_LTO option to enable LTO support in binutils. This is a blind option, selected by BR2_GCC_ENABLE_LTO. It just avoids having binutils.mk poke directly into gcc Config.in options. - Remove the check on the AVR32 special gcc version, which we don't support anymore. - Adapt the help text of the LTO Config.in option to no longer mention "Since version 4.5", since we only support gcc >= 4.5 in Buildroot anyway. - Fix typo in toolchain-external.mk comment.] Signed-off-by: Peter Kümmel <syntheticpp@gmx.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-03-06 13:34:06 +01:00
config BR2_BINUTILS_ENABLE_LTO
bool
binutils: make it a proper package * Convert binutils to a proper autotargets package * Add version 2.21 and drop version 2.17 * Hook up packaged binutils for target gcc * Build tools are on HOST_DIR now so change it * Move cross/host gcc to HOST_DIR * Drop kludge from commit 3c77bab2eeace3ee675bd745ca335fa3dd1630bb This is fixed in the next commit "gcc: install copies of libgcc, libstdc++ and libgcj to the sysroot" - tested for arm & x86_64 targets. * TARGET_CROSS now pointed to HOST_DIR too [Peter: Config.in tweaks] Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-12-31 12:39:01 +01:00
config BR2_BINUTILS_EXTRA_CONFIG_OPTIONS
fix whitespace
2006-07-17 05:53:12 +02:00
string "Additional binutils options"
default ""
help
- add binutils-2.18 and binutils-2.18.50.0.1
2007-09-17 13:19:04 +02:00
Any additional binutils options you may want to include.
Reference in New Issue Copy Permalink