buildroot/support, branch 2019.02-op-build

Restrict tar transform to regular files

2019-04-18T06:14:18+00:00

Without this restriction, symlinks are rewritten and corrupted. Example without the restriction: Input tree (valid): package-githash/file1 package-githash/link -> ./file1 Output tree (broken): package-githash/file1 package-githash/link -> package-githash/file1

Update for 2019.02

2019-03-04T21:49:56+00:00

Signed-off-by: Peter Korsgaard

config-fragments: drop old crosstool-ng toolchains

2019-03-04T15:26:20+00:00

These toolchains are very old and cause a number of autobuilder failures that doesn't happen with more recent toolchains: Fixes (glibc 2.18 does not provide O_TMPFILE): http://autobuild.buildroot.net/results/c49e8361a1d4406eefd8fc1b35c8e5b061aa403b Fixes (x86 toolchain built without libquadmath): http://autobuild.buildroot.net/results/2d9724f169ccd60c7feb1cb549f1e2e1e9219ac3/ Use Codesourcery ARM toolchain (GCC 4.8.3) to provide a test with a old GCC version. Signed-off-by: Peter Korsgaard

Revert "testing/tests/download: test git special ref"

2019-03-01T10:09:41+00:00

This reverts commit 81771cfcdc40e5909a4ec663e7c88b3a32068c05. The download of sha1 of a special ref currently works or not depending on the git client version in use. With git version 2.11.0 (present in the docker image) it does not work. With git version 2.17.1 it works. For the sake of reproducibility, remove this part of the TestGitRefs test case until some code gets added to the download infra to handle sha1 of a special ref for any git client version. Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/158295269 Signed-off-by: Ricardo Martincoski Cc: Arnout Vandecappelle Cc: Thomas Petazzoni Cc: Yann E. MORIN Signed-off-by: Peter Korsgaard

support/dependencies: require at least CMake 3.8

2019-03-01T09:10:30+00:00

gerbera package in version 1.3 unfortunately now requires CMake >= 3.8 for C++17 macros: https://github.com/gerbera/gerbera/commit/b5fd39f30fb10385ec228b71377685206a609c3a So we need to bump our requirement from 3.1 to 3.8. If the host doesn't have a CMake >= 3.8, Buildroot will build its own host-cmake package. Also drop patch that relax cmake requirement on json-for-modern-cpp Fixes: - http://autobuild.buildroot.org/results/6405647b47b132ff5d0d211b92d407322d52d507 Signed-off-by: Fabrice Fontaine Signed-off-by: Peter Korsgaard

support/config-fragments/autobuild: use external toolchains in RISC-V configs

2019-02-14T20:53:19+00:00

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 Cc: Mark Corbin Signed-off-by: Peter Korsgaard

support/config-fragments/autobuild: update all pre-built Buildroot toolchains

2019-02-14T20:52:40+00:00

All toolchains have been rebuilt with Buildroot 2019.02-rc1. Changes: - Toolchains that were using no-longer maintained kernel headers versions have been changed to use a variety of newer kernel headers versions (4.4, 4.9 or 4.14). - Since gcc 7.x is now the default in Buildroot, most toolchains that simply use the default gcc version use 7.x instead of 6.x. - br-arm-cortex-a9-glibc uses gcc 8.x, binutils 2.31 and kernel headers 4.20 Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

support/testing: build a glibc toolchain for docker / docker-compose tests

2019-02-12T19:03:46+00:00

runc (which is a reverse dependency of docker-engine) is about to gain a !uclibc dependency, so move to a glibc toolchain instead. There are currently no prebuilt x86_64 / core2 / glibc toolchains available, so instead use the internal toolchain backend to build one. While we are at it, drop the infra.basetest.BASIC_TOOLCHAIN_CONFIG reference, as that ARM toolchain configuration doesn't make any sense for this x86-64 based test. add docker / docker-compose tests Signed-off-by: Peter Korsgaard

support/scripts/pkg-stats: fix flake8 errors

2019-02-07T21:09:55+00:00

Fixes the following flake8 warnings: support/scripts/pkg-stats:34:2: W605 invalid escape sequence '\$' support/scripts/pkg-stats:34:4: W605 invalid escape sequence '$' support/scripts/pkg-stats:34:11: W605 invalid escape sequence '\$' support/scripts/pkg-stats:34:13: W605 invalid escape sequence '\(' support/scripts/pkg-stats:34:32: W605 invalid escape sequence '$' support/scripts/pkg-stats:34:34: W605 invalid escape sequence '\)' support/scripts/pkg-stats:35:2: W605 invalid escape sequence '\s' support/scripts/pkg-stats:35:14: W605 invalid escape sequence '\S' support/scripts/pkg-stats:35:17: W605 invalid escape sequence '\s' support/scripts/pkg-stats:42:1: E302 expected 2 blank lines, found 1 support/scripts/pkg-stats:587:133: E501 line too long (157 > 132 characters) Note that the "invalid escape sequence" errors work because Python leaves the \ in place if it doesn't recognise the escape sequence. But it's better practice to use a raw string for regular expressions. Signed-off-by: Arnout Vandecappelle (Essensium/Mind)

skeleton-custom: use a script to check merged usr structure

2019-02-06T16:03:30+00:00

Introduce support/scripts/check-merged-usr.sh, a script that check if a given path complies to the merged /usr requirements: / /bin -> usr/bin /lib -> usr/lib /sbin -> usr/sbin /usr/bin/ /usr/lib/ /usr/sbin/ Use this script in skeleton-custom.mk instead of a bunch of variables filled by $(shell ...) macros. The same script will be used to check rootfs overlays, in a forthcoming change. Signed-off-by: Carlos Santos Signed-off-by: Arnout Vandecappelle (Essensium/Mind)