From: "Oliver Smith-Denny via groups.io" <osde=linux.microsoft.com@groups.io>
To: devel@edk2.groups.io, richard.lyu@suse.com
Subject: Re: [edk2-devel] Current State of Build Reproducibility in edk2
Date: Fri, 27 Jun 2025 08:22:54 -0700 [thread overview]
Message-ID: <6175e4be-3150-41e3-9a4c-9ed0feb85004@linux.microsoft.com> (raw)
In-Reply-To: <aFq8zZK54XLllekM@localhost.localdomain>
Hi Richard,
Ah, so its my fault :). Thanks for pointing that out, that makes sense
of course. A partner team of mine is looking at build reproducibility
across environments, e.g. being able to reproduce what a pipeline
has built.
I think there is a path forward with using the same JSON file across
builds.
Thanks,
Oliver
On 6/24/2025 7:57 AM, Richard Lyu via groups.io wrote:
> Hi Oliver,
>
> I also noticed that edk2 is currently not reproducible in OvmfPkg because the stack cookie value has been randomized in AutoGen.h since edk2-stable202502. Fortunately, commit "cac0955658 BaseTools: Update Stack Cookie Logic" addresses this issue. By keeping the JSON files in the build directory, the STACK_COOKIE_VALUE can be made reproducible.
>
> I’ve tested this and was able to reproduce the same FDs and FVs with both edk2-stable202502 and edk2-stable202505. Perhaps you might like to give it a try as well.
>
> Best regards,
> Richard Lyu
>
>
>
> On 2025/06/19 09:53, Oliver Smith-Denny via groups.io wrote:
>> On 6/18/2025 5:21 PM, Michael D Kinney via groups.io wrote:
>>> Should work for physical platform builds.
>>>
>>> The OVMF and EmulatorPkg build may have some timestamps in them.
>>>
>>> If the EmbeddedPkg VirtualRealTimeClockLib is used, then it pulls in system time
>>> in Linux builds. I have a proposal to address this one queued up to support
>>> both windows and linux and reproducible builds when needed.
>>>
>>> [BuildOptions]
>>> GCC:*_*_*_CC_FLAGS = -DBUILD_EPOCH=`printenv SOURCE_DATE_EPOCH || date +%s`
>>>
>>> The following is a good resource on this topic and all the
>>> elements need to be tracked so issues do not get introduced.
>>>
>>> https://reproducible-builds.org/docs/
>>>
>>
>> Thanks, let me play around with this some more. It may be that the
>> platform I started trying this with had some similar dependencies.
>>
>> Thanks,
>> Oliver
>>
>>
>>
>>
>>
>>
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121436): https://edk2.groups.io/g/devel/message/121436
Mute This Topic: https://groups.io/mt/113714425/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2025-06-27 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 19:44 [edk2-devel] Current State of Build Reproducibility in edk2 Oliver Smith-Denny via groups.io
2025-06-19 0:21 ` Michael D Kinney via groups.io
2025-06-19 16:53 ` Oliver Smith-Denny via groups.io
2025-06-24 14:57 ` Richard Lyu via groups.io
2025-06-27 15:22 ` Oliver Smith-Denny via groups.io [this message]
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-list 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=6175e4be-3150-41e3-9a4c-9ed0feb85004@linux.microsoft.com \
--to=devel@edk2.groups.io \
/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