infra/pkg-kconfig: do not rely on package's .config as a timestamp
authorYann E. MORIN <yann.morin.1998@free.fr>
Thu, 30 May 2019 18:09:09 +0000 (20:09 +0200)
committerPeter Korsgaard <peter@korsgaard.com>
Thu, 30 May 2019 22:41:05 +0000 (00:41 +0200)
commit05fea6e4a60a38a797d9bacbf318a2cd7dbd435f
tree1d715071b77ebdbd5bdb6c15abdda8546bee3e01
parent46668b157a84713b894fc171af071a85ea9e96b8
infra/pkg-kconfig: do not rely on package's .config as a timestamp

Since linux-4.19, the kernel's build system internally touches its
.config file.

However, we currently used that file as a timestamp to detect whether
our kconfig fixups were to be (re)applied or not, which in turn is used
to decide whether we should (re)build the package or not.

But with latest kernel versions, this timestamp heuristic is now broken,
and we always rebuild the kernel on subsequent builds.

We fix that by introducing a separate timestamp file of our own, which
we know the kernel (or the kconfig-based packages, for that matters)
does not use.

Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Cc: Thomas De Schampheleire <patrickdepinguin@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
package/pkg-kconfig.mk