mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Mircea Ciocan <m.ciocan@ppc-ag.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Why are the __DATE__ and __TIME__ fixed in the OSELAS Toolchain or PTXDist ?
Date: Wed, 21 Jul 2021 15:02:36 +0200	[thread overview]
Message-ID: <ba835866-64fa-6deb-a4fd-4156a667fbc0@ppc-ag.de> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 799 bytes --]

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).

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 ?

Thanks and best regards,

Mircea










[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4266 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

             reply	other threads:[~2021-07-21 13:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21 13:02 Mircea Ciocan [this message]
2021-07-21 13:36 ` Alexander Dahl
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=ba835866-64fa-6deb-a4fd-4156a667fbc0@ppc-ag.de \
    --to=m.ciocan@ppc-ag.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