From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Casey Reeves <casey@xogium.me>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] boot/barebox: pass required environment variables for reproducible build
Date: Mon, 6 Feb 2023 09:54:04 +0100 [thread overview]
Message-ID: <20230206095404.3662d995@windsurf> (raw)
In-Reply-To: <20230119121004.3416962-3-casey@xogium.me>
On Thu, 19 Jan 2023 13:10:04 +0100
Casey Reeves <casey@xogium.me> wrote:
> Barebox makes use of the same variables as the linux kernel does for
> handling reproducible build -- KBUILD_BUILD_HOST,
> KBUILD_BUILD_TIMESTAMP, KBUILD_BUILD_USER. This patch sets the proper
> variables based on linux/linux.mk, and passes them to the make
> invocation when building, to ensure a reproducible build is possible
> when BR2_REPRODUCIBLE is enabled.
>
> Signed-off-by: Casey Reeves <casey@xogium.me>
> ---
> boot/barebox/barebox.mk | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-02-06 8:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 12:10 [Buildroot] [PATCH 0/2] make barebox build reproducible Casey Reeves
2023-01-19 12:10 ` [Buildroot] [PATCH 1/2] package/lzop: provide a patch to allow overriding of modification time Casey Reeves
2023-02-05 14:17 ` Thomas Petazzoni via buildroot
2023-01-19 12:10 ` [Buildroot] [PATCH 2/2] boot/barebox: pass required environment variables for reproducible build Casey Reeves
2023-02-06 8:54 ` Thomas Petazzoni via buildroot [this message]
2023-02-21 20:50 ` 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=20230206095404.3662d995@windsurf \
--to=buildroot@buildroot.org \
--cc=casey@xogium.me \
--cc=thomas.petazzoni@bootlin.com \
/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.