Adam Fedor wrote:
On Jan 31, 2006, at 12:28 AM, Stephen Sebeny wrote:
[EMAIL PROTECTED]:~/gui_test]> gmake
Making all for app GUITestApp...
Creating GUITestApp.app/....
Compiling file main.m ...
Linking app GUITestApp ...
Creating GUITestApp.app/Resources...
gmake[1]: *** Warning: File `GUITestApp.app' has modification time in the
future (2006-01-31 02:09:15.01342 > 2006-01-31 02:09:15.0127364)
Creating GUITestApp.app/Resources/Info-gnustep.plist...
Creating GUITestApp.app/Resources/GUITestApp.desktop...
gmake[1]: warning: Clock skew detected. Your build may be incomplete.
I've seen this happen when the files are on a networked server and the
server gets out-of-sync with the client. I don't know how to fix it
though. Sometimes it just goes away.
Here are some thing you can do about it:
1) Synch all machines to an NTP server regularly. (Hourly cron works) The nice
thing to do is set up one of your machines as a time master for your local
network which runs an ntp server daemon.
2) Write a script that 'touch'es all files in the build directory that have a
future date. You can get that automatically invoked in the make preamble if
you'd like.
In this case the clock skew is really small. Problem is that make warns for any
future time, including one less than a hundredth of a second in the future.
Note also that gmake has the -W FILE option so FILE is always considered new.
Regards,
Sheldon
_______________________________________________
Discuss-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/discuss-gnustep
