From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11641] New: linux kernel .config timestamp always out of date fixed with KCONFIG_NOSILENTUPDATE
Date: Thu, 24 Jan 2019 16:33:26 +0000 [thread overview]
Message-ID: <bug-11641-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11641
Bug ID: 11641
Summary: linux kernel .config timestamp always out of date
fixed with KCONFIG_NOSILENTUPDATE
Product: buildroot
Version: 2018.11.1
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: dcraw101 at yahoo.com
CC: buildroot at uclibc.org
Target Milestone: ---
Just noticed this when migrating from kernel 4.9 to 4.19. I noticed that now
in the linux kernel build dir the .config timestamp is always later than the
.stamp_kconfig_fixup_done. So every incremental buildroot make causes the
kernel build to always run starting at the kconfig fixup phase.
I traced the problem to somewhere in the kernel syncconfig step in the kernel
"build" phase. I think it is related to this new kernel 4.19 commit.
16952b77d8 kconfig: make syncconfig update .config regardless of
sym_change_count
If I define KCONFIG_NOSILENTUPDATE in my environment the problem goes away and
the timestamps are correct. Should buildroot set this env variable? I am not
sure what the other side affects would be.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-01-24 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 16:33 bugzilla at busybox.net [this message]
2019-08-15 13:19 ` [Buildroot] [Bug 11641] linux kernel .config timestamp always out of date fixed with KCONFIG_NOSILENTUPDATE bugzilla at busybox.net
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=bug-11641-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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.