Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <0a2701c21c7e$a61646d0$6132bc3e@BABEL> From: "Conrad Scott" To: "Harig, Mark A." , References: Subject: Re: [ANNOUNCEMENT] Updated: cygwin-1.3.11-3 Date: Tue, 25 Jun 2002 20:29:38 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 "Harig, Mark A." wrote: > The "solution"? I added step 1a. "sleep 1": > > 1. generate assembly language from c code > 1a. sleep 1 > 2. assemble the .asm into .o > 3. archive the .o into .a > > Should it be considered part of the standard Cygwin build > of 'make' that the '--disable-nsec-timestamps' be used > during configuration? There has been (AFAIK) no release of make since the patch for sub-second timestamps, so you will be using a version that has (effectively) been compiled with --disable-nsec-timestamps (unless you've compiled a copy for yourself recently). Has this problem just started? or have you been seeing this for some time? (which will help understand whether it's related to sub-second timestamps at all). // Conrad -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/