From: VGris AT aironet DOT com ("Griswold, Victor") Subject: Cygnus Win32 B17.1: Multiple file timestamp issues 25 Feb 1997 14:22:05 -0800 Approved: cygnus DOT gnu-win32 AT cygnus DOT com Distribution: cygnus Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Original-To: "'Cygnus:GNU-WIN32'" X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.994.63 Original-Sender: owner-gnu-win32 AT cygnus DOT com Gentlemen: Several cases exist within the Cygnus GNU-Win32 tools where file timestamps are or appear to be incorrectly handled. I know that at least one of these, the problem with 'tar' not setting file modification times correctly, has already been reported. My apologies if the other two below have also been reported. Case 1: files extracted via 'tar' are not set with the timestamp of the file within the archive. Case 2: 'cp -p' never preserves the modification time of the copied file. Case 3: (possibly different from the above) 'make' often complains of "modification time in the future" for files just created during execution of a Makefile. I run on a 180MHz Pentium Pro; if file time stamps "round up" time instead of truncate, given the poor quantum size of a FAT directory's file timestamp, it is entirely possible for my machine to create a derivative file "before" the parent file was created. My concern is less about annoying warning messages than about the manner in which this might subtly confuse the 'make' dependency algorithm. Victor J. Griswold, D.Sc. Aironet Wireless Communications, Inc. voice: 330-664-7987 fax: 330-664-7301 email: (MS-Mail) vgris AT aironet DOT com (MIME) Victor DOT Griswold AT pobox DOT com - For help on using this list, send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".