(forgot to forward to the list ><) On Thu, Jun 5, 2008 at 9:45 AM, EricDeb <[EMAIL PROTECTED]> wrote:
> > I just made a modification to the final step so that it will first echo out > to a text file and then perform the archiving step: > > $(LIBNAME) :: $(OBJFILENAMES) > echo a > $(@F).txt > $(AR) $(ARFLAGS) ./$(OBJFILE)/$(@F) $^ > > I then did a "ls --full-time" on three different files: 1. the .o file from > "the future", 2. the text file, 3. the library file from the archiver. In > this case, all of the timestamps are identical down to the second (anything > after the decimal point in seconds is 0 for all files). > > So, I am confused about what GNU Make is really complaining about. > :confused: > What's being claimed is "mtime of file isn't mtime that I expected, mate", i.e. "there's no bloody way that my file went 88MPH back into the future". Rick is correct though. Most of this time this implies either a clock skew between a fileserver and client, or a skew between the system clock when the file was made and when make stat's the file. - Is (I assume you're running Cygwin) up to date? - Are you absolutely sure that you're not running with a remote profile on a corporate server (I assume that because of your email address)? - Is Windows being run from a VM? HTH, -Garrett
_______________________________________________ Help-make mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-make
