X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Magnus Holmgren Subject: Re: /dev/null timing and clock skew problems Date: Fri, 9 Mar 2007 12:28:22 +0000 (UTC) Lines: 22 Message-ID: References: <028f01c75931$4c090e80$0200a8c0 AT AMD2500> <20070226105032 DOT GB5577 AT calimero DOT vinschen DOT de> <45E330B4 DOT 10507 AT portugalmail DOT pt> <45E3A3BA DOT 2070808 AT aol DOT com> <45E48273 DOT 2080003 AT portugalmail DOT pt> <06d901c75c3d$ed434e00$0700a8c0 AT AMD2500> <07af01c75d12$7b617ed0$0700a8c0 AT AMD2500> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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 be incomplete." can possibly > indicate an incomplete build. > This seems to be a problem on my slower machine XP, but not on my newer > Vista one. > > Were you getting clock skew problems too ? Yes, but they were caused by the imprecise file times (which triggers the clock skew message), as I was building on a FAT32 partition. Enabling the code in the #if statement fixed the file time issue, which only happened for files that were created during the build. Magnus -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/