Hmm. I think people should really stop using __DATE__ and __TIME__ as
a "normal" thing.
By patching the compiler, we are actually hiding the problem, not fixing it.
Sure, it will take more time and effort, but this is something that
each upstream author should really do, not something we should do in
their name to hide a problem which is really an upstream problem.
I wish people not end up thinking in the line of "oh, I don't have to
worry about __DATE__ and __TIME__ because dh and the C compiler takes
care of making it constant for a given package release".
Reproducible-builds mailing list