From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Why are the __DATE__ and __TIME__ fixed in the OSELAS Toolchain or PTXDist ?
Date: Wed, 21 Jul 2021 15:36:09 +0200 [thread overview]
Message-ID: <20210721133608.dy2urgqntrxzqseb@falbala.internal.home.lespocky.de> (raw)
In-Reply-To: <ba835866-64fa-6deb-a4fd-4156a667fbc0@ppc-ag.de>
[-- Attachment #1.1: Type: text/plain, Size: 1508 bytes --]
Hello Mircea,
On Wed, Jul 21, 2021 at 03:02:36PM +0200, Mircea Ciocan wrote:
> Hello everybody,
>
> I have a rather strange question:
>
> In one of my programs, to differentiate during testing in between different
> compilation of the same program, I'm using a poor's man serialization based
> on the __DATE__ and __TIME__ macros (or whatever they are nowadays).
I usually use some Git based version information from
`git describe --dirty` …
> Unfortunately I've always get a constant value: "Mar 1 2021-00:00:00" when
> I compile it with PTXDist and OSELAS toolchain and I was wondering where it
> comes from (this happens with the last three versions of the OSELAS
> toolchain)? This is for aarch64, the same program compiled with Ubuntu
> distribution gcc gives expected results.
>
> Could somebody shad some light why is that and eventually on how to disable
> this really undesired behavior ?
The reason is so called reproducible builds:
https://reproducible-builds.org/
You can change behaviour in your BSP through the
REPRODUCIBLE_TIMESTAMP_* variables. Access it from the menu through
"Project Name & Version" ---> "SOURCE_DATE_EPOCH timestamps source"
Greets
Alex
--
/"\ ASCII RIBBON | »With the first link, the chain is forged. The first
\ / CAMPAIGN | speech censured, the first thought forbidden, the
X AGAINST | first freedom denied, chains us all irrevocably.«
/ \ HTML MAIL | (Jean-Luc Picard, quoting Judge Aaron Satie)
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2021-07-21 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 13:02 Mircea Ciocan
2021-07-21 13:36 ` Alexander Dahl [this message]
2021-07-21 14:08 ` Mircea Ciocan
2021-07-21 17:35 ` Alexander Dahl
2021-07-21 15:35 ` Christian Melki
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=20210721133608.dy2urgqntrxzqseb@falbala.internal.home.lespocky.de \
--to=post@lespocky.de \
--cc=ptxdist@pengutronix.de \
/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