Re: /dev/null timing and clock skew problems

Aaron Gray writes: > > The #if statement starting on that line is just for the three second > > clearance. I use it on a local build of Make and it seems to work > > well. > > The " has modification time 0.0096 s in the future" were harmless. > > But the "Clock skew detected. Your build may b

Re: /dev/null timing and clock skew problems

Aaron Gray writes: > The code for this is available in standard Make, but it isn't enabled > in > the current build on Cygwin. (The code can be found in remake.c, at > line > 1277. It's currently enabled if WINDOWS32 or __MSDOS__ is defined.) Is this just the three second clearance or somethi

Re: /dev/null timing and clock skew problems

Aaron Gray writes: > > The code for this is available in standard Make, but it isn't enabled in > > the current build on Cygwin. (The code can be found in remake.c, at line > > 1277. It's currently enabled if WINDOWS32 or __MSDOS__ is defined.) > > Is this just the three second clearance or some

Re: /dev/null timing and clock skew problems

Pedro Alves writes: No, but I'm on FAT32 on this machine. Problem is described here: http://www.delorie.com/djgpp/v2faq/faq22_18.html According to that same page, DJGPP has a local hack^Wpatch to suppress that warning: "DJGPP ports of GNU Make v3.77 and later allow for up to 3 seconds of pos

Re: /dev/null timing and clock skew problems

Pedro Alves writes: > No, but I'm on FAT32 on this machine. Problem is described here: > > http://www.delorie.com/djgpp/v2faq/faq22_18.html > > According to that same page, DJGPP has a local hack^Wpatch to > suppress that warning: > > "DJGPP ports of GNU Make v3.77 and later allow for up to >

Re: /dev/null timing and clock skew problems

It seems the 'Clock Skew' warnings are the only serious ones. They never used to occur on previous Cygwin releases though. I am building LLVM with Cygwin and am getting the warnings but on building GCC I am getting no clock skew or modification time warnings. http://llvm.org CVS and buil

Re: /dev/null timing and clock skew problems

Tim Prince escreveu: [EMAIL PROTECTED] wrote: I see this a lot on regular files. I just got this: make: Warning: File `Makefile' has modification time 0.42 s in the future If you are accessing files on another machine, and you aren't using any means for keeping the date clocks synchronized,

Re: /dev/null timing and clock skew problems

[EMAIL PROTECTED] wrote: I see this a lot on regular files. I just got this: make: Warning: File `Makefile' has modification time 0.42 s in the future If you are accessing files on another machine, and you aren't using any means for keeping the date clocks synchronized, this is to be expected

Re: /dev/null timing and clock skew problems

Corinna Vinschen escreveu: On Feb 25 23:04, Aaron Gray wrote: I am doing make based builds on Cygwin and am getting following warning messages multiple times in stdout :- make[2]: Warning: File `/dev/null' has modification time 0.0096 s in the future make[2]: warning: Clock s

Re: /dev/null timing and clock skew problems

On Feb 25 23:04, Aaron Gray wrote: > I am doing make based builds on Cygwin and am getting following warning > messages multiple times in stdout :- > >make[2]: Warning: File `/dev/null' has modification time 0.0096 s in > the future > >make[2]: warning: Clock skew detected. Yo

/dev/null timing and clock skew problems

I am doing make based builds on Cygwin and am getting following warning messages multiple times in stdout :- make[2]: Warning: File `/dev/null' has modification time 0.0096 s in the future make[2]: warning: Clock skew detected. Your build may be incomplete. I am using Windo