From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] infra/pkg-kconfig: do not rely on package's .config as a timestamp
Date: Fri, 31 May 2019 00:41:48 +0200 [thread overview]
Message-ID: <87y32nwonn.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190530180909.14418-1-yann.morin.1998@free.fr> (Yann E. MORIN's message of "Thu, 30 May 2019 20:09:09 +0200")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> 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 spearate 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>
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-05-30 22:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 18:09 [Buildroot] [PATCH] infra/pkg-kconfig: do not rely on package's .config as a timestamp Yann E. MORIN
2019-05-30 22:41 ` Peter Korsgaard [this message]
2019-05-31 18:41 ` Yann E. MORIN
2019-05-31 20:53 ` Peter Korsgaard
2019-06-06 15:33 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y32nwonn.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.