https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107351
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Sergei Trofimovich from comment #4)
> Attached the build log.
>
> I completely forgot about the fact that I was using gcc source from
> "normalized" filesystem which intentionally resets all timestamps (it's one
> of the build modes for my distribution to validate build determinism):
>
> $ LANG=C ls -l
> /nix/store/p2m8xz3klafr1ydbjf8g86vmylziscr3-source/gcc/cp/module.cc
> -r--r--r-- 4 root root 533735 Jan 1 1970
> /nix/store/p2m8xz3klafr1ydbjf8g86vmylziscr3-source/gcc/cp/module.cc
>
> Silly question: would it be reasonable for module.cc to use
> gcc/{BASE-VER,DATESTAMP}?
The problem with DATESTAMP is that it changes every day while module support
does not. So this might be ok.
You might be one of the few which does the reset timestamp stuff and even then
it seems like it could be broken ...
