71ce6efa3c
We currently do the Linux build as follows: make <imagename> if modules enabled; make modules; fi However, Clement Léger recently reported that due to us not using the "all" target, the GDB scripts that the kernel can build when CONFIG_GDB_SCRIPTS is enabled are not built, since upstream kernel commit 67274c083438340ad16c1437caebc84e1253b224 (merged in v5.1) moved that logic to a separate scripts_gdb target, which is a dependency of the "all" target. While we could add some more logic to explicit generate the "scripts_gdb" target, this logic would fail on Linux < 5.1 for which this make target doesn't exist. So instead, let's simplify the build logic, and use: make all <imagename> The "all" target automatically depends on "modules" if CONFIG_MODULES is set, so we no longer need to explicit generate the "modules" target separately. As a result of this change, we may generate additional kernel images compared to what was done previously, but such images would anyway not be installed, and the additional build time is minimal. We did some research as to why the kernel build was done like this in Buildroot, and it's been like that since linux/linux.mk was added back in 2010 by commit |
||
---|---|---|
.. | ||
0001-timeconst.pl-Eliminate-Perl-warning.patch.conditional | ||
Config.ext.in | ||
Config.in | ||
linux-ext-aufs.mk | ||
linux-ext-ev3dev-linux-drivers.mk | ||
linux-ext-fbtft.mk | ||
linux-ext-rtai.mk | ||
linux-ext-xenomai.mk | ||
linux.hash | ||
linux.mk |