staging/chunkeey/include/prereq-build.mk, branch v19.07.9

Extend checks on build prerequisites for building OpenWRT core

2021-05-08T10:51:54Z

OpenWRT requires a number of Perl modules to be installed. It wasn't checking on all of them. This patch adds checks for Perl FindBin, File::Copy, File::Compare and Thread::Queue modules. Failing to install these, will have the build break at some point. By adding these to the prereq-build.mk script, they are checked on forehand. Tested on a Fedora 33 and 34 (beta) that was freshly installed. Fedora appears to break up Perl modules into small packages that need to be installed for the build to succeed. Signed-off-by: Bas Mevissen (cherry picked from commit f68c9474acf9a65b5a9538db8e45c173462487e3)

prereq-build: test for perl's Data::Dumper

2021-05-08T10:50:49Z

Required for installation of autoconf: make[5]: Entering directory `/openwrt/build_dir/host/autoconf-2.69' Making all in bin make[6]: Entering directory `/openwrt/build_dir/host/autoconf-2.69/bin' autom4te_perllibdir='..'/lib AUTOM4TE_CFG='../lib/autom4te.cfg' ../bin/autom4te -B '..'/lib -B '..'/lib --language M4sh --cache '' --melt ./autoconf.as -o autoconf.in Can't locate Data/Dumper.pm in @INC (@INC contains: ../lib /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at ../lib/Autom4te/C4che.pm line 33. BEGIN failed--compilation aborted at ../lib/Autom4te/C4che.pm line 33. Compilation failed in require at ../bin/autom4te line 40. BEGIN failed--compilation aborted at ../bin/autom4te line 40. make[6]: *** [autoconf.in] Error 2 Signed-off-by: Rosen Penev (cherry picked from commit dc467eac38f2447b652b6680cf4af75b05fd6cd2)

build: fix checks for GCC11

2021-03-06T14:48:03Z

Fedora 34 already uses GCC11. Reported-by: Marcin Juszkiewicz Signed-off-by: Petr Štetiar (cherry picked from commit cae69d558135456976b8fc6cb08530d1358cf6d5)

build/prereq: merge ifndef IB block together

2020-12-31T19:33:07Z

Multiple prereq checks are only required within the build system but not for the ImageBuilder. These checks are excluded by using ifndef IB. This commit merges the three ifndef IB blocks together. Signed-off-by: Paul Spooren (cherry picked from commit cc9d5b5a488d3a43068f621a1ef184f06e43bede)

build, imagebuilder: Do not require compilers

2020-12-31T19:32:33Z

The buildroot and SDK both require the compilers (gcc, g++) to be installed on the host system, however the ImageBuilder uses precompiled binaries. This patch changes the prerequirements checks to skip the checking for the compilers if running as ImageBuilder. A similar change has been made for libncurses-dev in 4a1a58a3e2d2. Signed-off-by: Sven Roederer Acked-by: Paul Spooren (cherry picked from commit ae12a747cae3df16d84b7dc92f39427948d4e8e2)

build, imagebuilder: Do not require libncurses-dev

2020-12-31T19:31:54Z

The buildroot and SDK both require `libncurses-dev` to be installed on the system, however the ImageBuilder uses precompiled binaries. This patch changes the prerequirements checks to skip the `libncurses-dev` part if running as ImageBuilder. Signed-off-by: Paul Spooren (cherry picked from commit 4a1a58a3e2d2360950ff23a05f1f55b779174d6a)

build: prereq: tidy gcc version checks

2020-03-29T16:47:03Z

There is a restriction in the number of parameters(10) that may be passed to the SetupHostCommand macro so continually adding explicit gcc'n' version checks ends up breaking the compiler check for the later versions and oddballs like Darwin as was done in 835d1c68a0 which added gcc10. Drop all the explicitly specified gcc version checks. If a suitable gcc compiler is not found, it may be specified at the dependency checking stage after which that version will be symlinked into the build staging host directory. eg. 'CC=gccfoo CXX=g++foo make prereq' Signed-off-by: Kevin Darbyshire-Bryant Acked-by: Jo-Philipp Wich (cherry picked from commit 1fb3c003d68d3feaf797e8b64edccc9fa622d250)

build: add GCC 10 version detection

2020-03-29T16:46:57Z

Lets add GCC 10 detection to the build system as distributions like Fedora 32 have started shipping with it. Some tools like mtd-utils need work to compile under GCC10, but that will be next step. Signed-off-by: Robert Marko (cherry picked from commit 835d1c68a0f036c8b0d837a48b5a05fdfb2e8218)

build: cleanup possibly dangling Python 3 host symlink

2019-11-09T07:21:45Z

When switching from master branch to 19.07 or older, we need to ensure that Python symlink in staging bin directory points to Python 2. We can't rely completly just on SetupHostCommand as its executed only in cases when the $(STAGING_DIR_HOST)/bin/python doesn't already exist, so we need to remove it before running SetupHostCommand. This is a cherry-pick of 3b68fb57c938af3948ae4c2da61501183fbef649 with python3 instead of python2 Signed-off-by: Petr Štetiar Signed-off-by: Etienne Champetier

build: fixup python SetupHostCommand to use python2

2019-11-09T07:21:45Z

Here is a way to break your build env without this patch: 1) have python point to python3, and no python2 2) start the build, SetupHostCommand will create a symlink ./staging_dir/host/bin/python -> /usr/bin/python 3) build fails on scons because it can't find any python2 4) install python2 and restart the build 5) the build fails on wireless-regdb compile because python is python3 instead of python Signed-off-by: Etienne Champetier