From: Nathan Bloch <nblochn@gmail.com>
To: buildroot@buildroot.org
Cc: Nathan Bloch <nblochn@gmail.com>
Subject: [Buildroot] [PATCH] pkg-generic: suppress SOURCE_DATE_EPOCH warning in step_time
Date: Thu, 19 Mar 2026 12:42:49 +0200 [thread overview]
Message-ID: <20260319104249.22286-1-Nathan.B@solaredge.com> (raw)
From: Nathan Bloch <nblochn@gmail.com>
The step_time hook calls date +%s.%N to measure build step elapsed time.
When SOURCE_DATE_EPOCH is set (for reproducible builds), GNU coreutils date
emits "Warning: using $SOURCE_DATE_EPOCH instead of true time" for every
call — twice per step, across all packages, resulting in hundreds of noisy
log lines.
Unset SOURCE_DATE_EPOCH inline for these timing-only calls, since they
measure real elapsed time and do not affect build reproducibility.
Signed-off-by: Nathan Bloch <nblochn@gmail.com>
---
package/pkg-generic.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/pkg-generic.mk b/package/pkg-generic.mk
index a2749320..e4bf6def 100644
--- a/package/pkg-generic.mk
+++ b/package/pkg-generic.mk
@@ -50,7 +50,7 @@ endef
# Time steps
define step_time
printf "%s:%-5.5s:%-20.20s: %s\n" \
- "$$(date +%s.%N)" "$(1)" "$(2)" "$(3)" \
+ "$$(SOURCE_DATE_EPOCH= date +%s.%N)" "$(1)" "$(2)" "$(3)" \
>>"$(BUILD_DIR)/build-time.log"
endef
GLOBAL_INSTRUMENTATION_HOOKS += step_time
--
2.34.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-03-19 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 10:42 Nathan Bloch [this message]
2026-04-07 18:42 ` [Buildroot] [PATCH] pkg-generic: suppress SOURCE_DATE_EPOCH warning in step_time Arnout Vandecappelle via buildroot
2026-04-08 9:29 ` Nicolas Cavallari
2026-04-08 9:57 ` Arnout Vandecappelle via buildroot
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=20260319104249.22286-1-Nathan.B@solaredge.com \
--to=nblochn@gmail.com \
--cc=buildroot@buildroot.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox