This is the mail archive of the
mailing list for the Cygwin project.
Re: make problem/bug on NT (Cygwin B19)
- To: "John A. Turner" <John dot Turner at pobox dot com>
- Subject: Re: make problem/bug on NT (Cygwin B19)
- From: "Lassi A. Tuura" <lat at iki dot fi>
- Date: Mon, 17 Aug 1998 09:48:26 +0200 (METDST)
- cc: gnu-win32 mailing list <gnu-win32 at cygnus dot com>, bug-gnu-utils at prep dot ai dot mit dot edu
- Reply-To: "Lassi A. Tuura" <lat at iki dot fi>
|> Does anyone have a clue what might be happening here? [...] v3.77 of
|> make [...] seemed to have other problems (kept claiming times were
Actually, that likely to be your problem. If the modification time of
the library is in future (beyond the time stamp you get on your .f90
file after touching it), make will think it is up to date and will not
build anything. Perhaps the `lb' tool is doing something twisted?
In general, if make spits out messages like `Clock skew detected, your
build may be incomplete', watch out. Your build *may* be incomplete :-)
Usually things like these happen only on networked file systems, where
the file server and the client run different times. Building on a local
file system usually succeeds in that situation. You should make sure
your client is always running at the same time, or more in future, than
your file server (for instance, by using a network time protocol).
Otherwise, as files are created on the server, they get future (as seen
by your workstation) timestamps and make will be confused.
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going
to land, and it could be dangerous sitting under them as they fly
overhead. --RFC1925, "The Twelve Networking Truths"
For help on using this list (especially unsubscribing), send a message to
"email@example.com" with one line of text: "help".