help-make
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Clock skew detected, how to fix?


From: EricDeb
Subject: Clock skew detected, how to fix?
Date: Wed, 4 Jun 2008 12:55:06 -0700 (PDT)

First, I'm using Cygwin on a Windows machine with GNU Make 3.81. I have a
feeling this particular problem is not platform dependent so I'm asking
here.

I've setup the make to take advantage of the compiler's ability to accept
multiple input files in a single invocation. The reason for this is to
reduce the load on our license server and reduce compile times. I did this
with the following:

$(LIBNAME) :: $(CFILES)
        $(CC) -c $(CFLAGS) $(CPPFLAGS) $?

OBJFILENAMES = $(patsubst %.c,%.o,$(CFILES))

$(LIBNAME) :: $(OBJFILENAMES)   
        $(AR) $(ARFLAGS) ./$(OBJFILE)/$(@F) $^

Where CFILES is a space delimited list of source files ending in .C. Make
happily runs our compiler "armcc" with multiple files. (It's fun to see it
compile over a hundred files at once). But then, Make gets to run the
archiver "armar" and reports something like this:

make[2]: Warning: File `foo.o' has modification time 0.43 s in the future

and then when exiting the submake it reports:

make[2]: warning:  Clock skew detected.  Your build may be incomplete.

As far as I can tell, this creates no actual build problems, but it is
annoying and can mask true build errors with spam. Any advice on how I can
avoid getting this error? Perhaps something with .LOW_RESOLUTION_TIME?
-- 
View this message in context: 
http://www.nabble.com/Clock-skew-detected%2C-how-to-fix--tp17655253p17655253.html
Sent from the Gnu - Make - Help mailing list archive at Nabble.com.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]