%% Doug Shea <[EMAIL PROTECTED]> writes:
ds> I see. Does that mean that a well-placed "sleep" command somewhere
ds> in the makefile might make it work? Say, after creating those
ds> files, hang out for a bit to let the timestamp become sane, and
ds> then proceed?
Well, yes, but that's a
Title: RE: File list hash not updated (FAT32 problem)
I see. Does that mean that a well-placed "sleep" command somewhere in the makefile might make it work? Say, after creating those files, hang out for a bit to let the timestamp become sane, and then proceed?
--
%% Doug Shea <[EMAIL PROTECTED]> writes:
ds> An update to this... I believe I've found the problem: it doesn't
ds> work when run on files in a FAT32 filesystem.
FAT32 has a bogus feature: timestamps have only 2 second (or was it 3?)
granularity, not 1 second. There is some code to deal with
Title: RE: File list hash not updated (FAT32 problem)
An update to this... I believe I've found the problem: it doesn't work when run on files in a FAT32 filesystem. I've made a sample makefile, below. This makefile breaks on Win98 or Win2k, using the 3.77 and 3.79.1 g
Title: File list hash not updated
I'm seeing an odd behavior, and can't figure out what it might be. We using VPATH, and we're using it to find source files. One of the directories in the path only has two files in it when the make begins, but gets populated with more
