NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
a3bd098356
kumquat-buildroot/support/config-fragments/autobuild/br-mips64-n64-full.config

11 lines
370 B
Plaintext
Raw Normal View History

support: add autobuild toolchain config fragments We currently have a list of toolchain configurations that are used by the autobuilders at [1]. However, this makes it a little more difficult for people to use these configurations, and also to have a different list of configurations for different branches. For example if a new architecture is introduced, the 2017.02.x branch doesn't have support for this architecture yet so it shouldn't try to run those configs. Therefore, include the autobuild config fragments directly in Buildroot, so they can be branched together with the rest. We create a new directory under support/ to store them. Generated with wget -nd --no-parent --recursive http://autobuild.buildroot.net/toolchains/configs/ The index.html file is removed. The toolchain-configs.csv file is adapted so the URLs become relative paths pointing to the config fragments. [1] http://autobuild.buildroot.net/toolchains/configs/toolchain-configs.csv Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-07-21 03:05:23 +02:00
BR2_mips64el=y
BR2_MIPS_NABI64=y
# BR2_MIPS_SOFT_FLOAT is not set
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD=y
support/config-fragments/autobuild: update pre-built Buildroot toolchains All pre-built Buildroot toolchains have been rebuilt with Buildroot 2018.05, so this commit updates the corresponding configuration fragments to make sure the autobuilders use the new toolchains. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-06-30 18:00:30 +02:00
BR2_TOOLCHAIN_EXTERNAL_URL="http://autobuild.buildroot.org/toolchains/tarballs/br-mips64-n64-full-2018.05.tar.bz2"
support/config-fragments/autobuild: update toolchains for 2017.11-rc1 All Buildroot pre-built toolchains have been rebuilt with Buildroot 2017.11-rc1, so that they have the latest version of glibc/musl/uClibc, and also the latest gcc/binutils updates. Specifically, this will fix the build failures on Blackfin that were due to the missing accept4() support: http://autobuild.buildroot.net/results/8b5a72dd7cde685f6f68f46aeee8b1b60c96d559/ (openobex) http://autobuild.buildroot.net/results/b19dd9ed29944d7f79c6f824669e3baaa0bb045a/ (libiio) In terms of changes to the toolchains: - AArch64 glibc toolchain changed to use 4.4 kernel headers instead of 4.1, in order to increase the variety of kernel header versions being tested. - Most configurations now use 4.13 kernel headers instead of 4.12 (except the configurations that were explicitly using an older kernel headers version) - The mips64 n64 configuration is changed from using gcc 4.9 to gcc 5, since another ARM configuration already tests gcc 4.9. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-11-07 15:21:43 +01:00
BR2_TOOLCHAIN_EXTERNAL_GCC_5=y
support/config-fragments/autobuild: update all Buildroot pre-built toolchains This commit updates all the pre-built Buildroot toolchains, which have all been rebuilt with Buildroot as of commit 046c5e2. The initial motivation for this update is that an upcoming bump of procps-ng uses fopencookie(), which has only been introduced in musl 1.1.19, which itself started being used in Buildroot after the 2018.02 release. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-19 22:26:54 +02:00
BR2_TOOLCHAIN_EXTERNAL_HEADERS_4_16=y
support: add autobuild toolchain config fragments We currently have a list of toolchain configurations that are used by the autobuilders at [1]. However, this makes it a little more difficult for people to use these configurations, and also to have a different list of configurations for different branches. For example if a new architecture is introduced, the 2017.02.x branch doesn't have support for this architecture yet so it shouldn't try to run those configs. Therefore, include the autobuild config fragments directly in Buildroot, so they can be branched together with the rest. We create a new directory under support/ to store them. Generated with wget -nd --no-parent --recursive http://autobuild.buildroot.net/toolchains/configs/ The index.html file is removed. The toolchain-configs.csv file is adapted so the URLs become relative paths pointing to the config fragments. [1] http://autobuild.buildroot.net/toolchains/configs/toolchain-configs.csv Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-07-21 03:05:23 +02:00
BR2_TOOLCHAIN_EXTERNAL_LOCALE=y
BR2_TOOLCHAIN_EXTERNAL_CXX=y
Reference in New Issue Copy Permalink