Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: N8TM AT aol DOT com Message-ID: <9a.a3919f.25cb34e4@aol.com> Date: Thu, 3 Feb 2000 14:45:40 EST Subject: Re: Compiling Scilab and Octave: To: glenn DOT fulford AT paradise DOT net DOT nz CC: cygwin AT sourceware DOT cygnus DOT com MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Unknown (No Version) In a message dated Thu, 3 Feb 2000 1:52:02 PM Eastern Standard Time, "Glenn R. Fulford" writes: > > running ./configure > configure warning: > > I didn't find -ltermcap, -lterminfo, -lncurses, -lcurses or -ltermlib > Aren't there add-on packages intended to support these? > > Make errors: > > --- Clock skew detected. > > --- File ... has modification time in the future > 2000-01-31 20:11:10 > 2000-01-31 20:11:09 > This appears to be a typical characteristic of Windows systems, as if the low order bits of the file time are "random." It hasn't appeared to be a problem; I don't see it as often in Win2K. I've wondered whether cygwin should mask off the low order bits, given that Windows works this way. > > Any help you can give me will be certainly appreciated. > Thanks very much. Glenn. > > Glenn Fulford -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com