From: Peter Korsgaard <peter@korsgaard.com>
To: opensbi@lists.infradead.org
Subject: [PATCH v5] Makefile: Add build time and compiler info string
Date: Mon, 18 Oct 2021 13:40:19 +0200 [thread overview]
Message-ID: <87lf2qef30.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAEUhbmVTNMp2Y5CCJNZZH4ph5tmBST5hkP6e+Xg8Cb9Sjxqt6g@mail.gmail.com> (Bin Meng's message of "Mon, 18 Oct 2021 18:33:59 +0800")
>>>>> "Bin" == Bin Meng <bmeng.cn@gmail.com> writes:
Hi,
>> Users will have to figure-out/remember a fixed build date when
>> using SOURCE_DATA_EPOCH for reproducible builds whereas
>> users don't need to do anything when BUILD_INFO is not defined.
> This is not 100% true as with current OpenSBI we never claim its build
> is fully reproducible. For example, one can easily add __DATE__ to the
> source codes which will alter unless we provide SOURCE_DATA_EPOCH.
Notice that GCC >= 7 does in fact look for SOURCE_DATE_EPOCH in the
environment and change the behaviour of the __DATE__ / __TIME__ macros:
https://gcc.gnu.org/onlinedocs/cpp/Environment-Variables.html
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2021-10-18 11:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 4:11 [PATCH v5] Makefile: Add build time and compiler info string Anup Patel
2021-10-18 4:29 ` Alistair Francis
2021-10-18 5:57 ` Bin Meng
2021-10-18 6:17 ` Anup Patel
2021-10-18 6:21 ` Bin Meng
2021-10-18 7:44 ` Andreas Schwab
2021-10-18 8:12 ` Bin Meng
2021-10-18 10:08 ` Anup Patel
2021-10-18 10:10 ` Bin Meng
2021-10-18 10:19 ` Anup Patel
2021-10-18 10:28 ` Andreas Schwab
2021-10-18 10:36 ` Anup Patel
2021-10-19 0:23 ` Alistair Francis
2021-10-19 0:46 ` Bin Meng
2021-10-18 10:33 ` Bin Meng
2021-10-18 11:40 ` Peter Korsgaard [this message]
2021-10-18 6:18 ` 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=87lf2qef30.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=opensbi@lists.infradead.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 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.