Well, it's confusing because I have 3 machines. 1. WinXP (cygwin 1.5.19) - once built, the timestamps are equal and no problem( happy with that, but I got the point that this is wrong makefile design)
2. Win7 (cygwin 1.7.5) - once built, the timestamps are equal, and no further build required if files are intact. However, sometimes the timestamps are not equal and it doesn't consider targets up to date. 3. Another Win7 (cygwin 1.7.5, I can check exactly later) - timestamps are always different, hence it's NEVER up to date. This is the original case I was talking about. Hope it's clear now. Sorry for misleading and confusing you ^^ Dave Korn-6 wrote: > > On 06/05/2010 01:45, MichaelKim wrote: >> Just to make sure we are on the same page.. Whenever the timestamps are >> equal, it doesn't consider target as out of date, hence nothing happens. > > Heh, it's as well you said that, I had it the wrong way around. I'm not > clear now: the subject says 'never' up to date, but do you also mean that > sometimes it gets it right anyway? That would be strange. > > cheers, > DaveK > > > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > > -- View this message in context: http://old.nabble.com/Cygwin-make-target-is-never-determined-up-to-date-tp28454344p28468326.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
