NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
83268eb4d0
kumquat-buildroot/support/config-fragments/autobuild/br-riscv32.config

10 lines
336 B
Plaintext
Raw Normal View History

support/config-fragments/autobuild: use external toolchains in RISC-V configs This commit replaces the two RISC-V configurations used for the autobuilders to use pre-built external toolchains rather than internal toolchains. This saves quite a bit of build time in the autobuilders, and also allows people to reproduce build issues in a much more efficient way, since rebuilding the toolchain is not needed. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Mark Corbin <mark.corbin@embecosm.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-02-14 11:36:19 +01:00
BR2_riscv=y
BR2_RISCV_32=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD=y
support/config-fragments/autobuild: update toolchains to 2019.05.1 All toolchains have been rebuilt with Buildroot 2019.05.1. A number of toolchains are now using Linux headers 5.1 instead of 4.19, because 5.1 is now the default version. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-08-02 22:51:47 +02:00
BR2_TOOLCHAIN_EXTERNAL_URL="http://autobuild.buildroot.net/toolchains/tarballs/br-riscv32-glibc-2019.05.1.tar.bz2"
support/config-fragments/autobuild: set gcc version for RISC-V toolchains Prior to b3ba26150d49dbc6b06ad402c5f6fbd398a71451 ("toolchain/toolchain-external/toolchain-external-custom: be more flexible on gcc version"), the default gcc version selected by Buildroot for custom external toolchain was affected by the BR2_ARCH_NEEDS_GCC_AT_LEAST_xyz definitions. Since BR2_riscv selects BR2_ARCH_NEEDS_GCC_AT_LEAST_7, gcc 7.x was the default gcc version assumed to be used in a custom RISC-V external toolchain, so our config snippets for RISC-V toolchains were correct. With b3ba26150d49dbc6b06ad402c5f6fbd398a71451 applied, the default gcc version assumed for custom external toolchains is the latest one (currently gcc 9.x), while our RISC-V toolchains use gcc 7.x. So we now need to explicitly give the gcc version used by our RISC-V toolchains, otherwise the build fails with: Incorrect selection of gcc version: expected 9.x, got 7.4.0 Fixes: http://autobuild.buildroot.net/results/b872befe1adec2633b9cbcc49bc0eb7619f606c2/ Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-08-04 08:50:48 +02:00
BR2_TOOLCHAIN_EXTERNAL_GCC_7=y
support/config-fragments/autobuild: update toolchains to 2019.05.1 All toolchains have been rebuilt with Buildroot 2019.05.1. A number of toolchains are now using Linux headers 5.1 instead of 4.19, because 5.1 is now the default version. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-08-02 22:51:47 +02:00
BR2_TOOLCHAIN_EXTERNAL_HEADERS_5_0=y
support/config-fragments/autobuild: use external toolchains in RISC-V configs This commit replaces the two RISC-V configurations used for the autobuilders to use pre-built external toolchains rather than internal toolchains. This saves quite a bit of build time in the autobuilders, and also allows people to reproduce build issues in a much more efficient way, since rebuilding the toolchain is not needed. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Mark Corbin <mark.corbin@embecosm.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-02-14 11:36:19 +01:00
BR2_TOOLCHAIN_EXTERNAL_CUSTOM_GLIBC=y
BR2_TOOLCHAIN_EXTERNAL_CXX=y
Reference in New Issue Copy Permalink