Re: [ptxdist] Why are the __DATE__ and __TIME__ fixed in the OSELAS Toolchain or PTXDist ?

[Christian Melki <christian.melki@t2data.com>]

On 7/21/21 3:02 PM, 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).
> 

Which program?

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

I have the same issue with U-boot 2021.07 atleast, but I find it hard to
believe that ptxdist is behind all this.
Usually it involves some complex timestamp generation depending on a
bucketload of things in some makefile.
Maybe look there?

Could be that ptxdist is missing some environment variable or something?

> Could somebody shad some light why is that and eventually on how to 
> disable this really undesired behavior ?
> 
> Thanks and best regards,
> 
> Mircea
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
> To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
> 


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de