[hatari-devel] Strange timestamp issue

[Uwe Seimet <Uwe.Seimet@xxxxxxxxx>]

Hi,

When compiling with Pure C I have an issue with the timestamps of the .C and
..O files. When I save a .C file in the Pure C editor it will automatically be
recompiled when I trigger the Pure C make process. After the new .O file has
been created, when I trigger the make process again, Pure C again compiles
this file, even though nothing should be done anymore. With a real Atari
there is no such problem, i.e. Pure C correctly detects that the .O file is
newer than then .C file.

When looking at the timestamps in bash this is what I get right after saving
the .C file in Pure C:

-rw-rw-r-- 1 us users 76956 Jul 26  2024 PART.C
-rw-rw-r-- 1 us users 53080 Jul 26 23:00 PART.O

There is a date but no timestamp for PART.C. After some time (about a
minute) the timestamp appears without any further action on my side:

-rw-rw-r-- 1 us users 76956 Jul 26 23:02 PART.C
-rw-rw-r-- 1 us users 53080 Jul 26 23:00 PART.O

As far as I can tell, as long as the shell does not display a timestamp Pure
C thinks that the .C file is newer than the corresponding object file and
recompiles it.

Note that the "lazytime" option is active for my filesystems, but I don't
think this is related, because in Linux this has not caused me any troubles
for ages, e.g. when using make or cmake with Linux.

Any idea what's happening here, and why only Hatari seems to be affected?

Best regards

Uwe