Re: Cygwin make target is never determined up to date

2010-05-05 Thread MichaelKim
You've got my point and I'll report the exact dll version later today. However, I redesigned the makefile in order to avoid such bad dependency. Dave Korn-6 wrote: > > On 06/05/2010 02:15, MichaelKim wrote: >> Well, it's confusing because I have 3 machines. >

Re: Cygwin make target is never determined up to date

2010-05-05 Thread MichaelKim
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

Re: Cygwin make target is never determined up to date

2010-05-05 Thread MichaelKim
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. Dave Korn-6 wrote: > > On 06/05/2010 01:16, MichaelKim wrote: > >> The timestamps are equal most of the time, just sometimes

Re: Cygwin make target is never determined up to date

2010-05-05 Thread MichaelKim
47000 +0900 Change: 2010-05-06 07:57:25.47000 +0900 This output is from 1.7.5 on Win7, which I downloaded/installed 2 days ago. The timestamps are equal most of the time, just sometimes it may happen be different. Dave Korn-6 wrote: > > On 06/05/2010 00:46, MichaelKim wrote: >>

Re: Cygwin make target is never determined up to date

2010-05-05 Thread MichaelKim
I mentioned above. Dave Korn-6 wrote: > > On 06/05/2010 00:23, MichaelKim wrote: > >> But it's not related to WinXP or Win7, because it also worked >> _incorrectly_ >> on other Win7. >> So what is happening that in some cases the mtime of directory is ex

Re: Cygwin make target is never determined up to date

2010-05-05 Thread MichaelKim
le created. This is confusing. @DaveK: I'll check the article for sure, thanks! Dave Korn-6 wrote: > > On 05/05/2010 06:04, Jeremy Bopp wrote: >> MichaelKim wrote: > >>> Prerequisite `../bin/build/chrome' is newer than >>> t

Re: Cygwin make target is never determined up to date

2010-05-04 Thread MichaelKim
3:03:01.090960400 +0900 Change: 2010-05-05 13:03:01.090960400 +0900 as you can see `chrome` dir is really newer than `alt.jar` Jeremy Bopp-3 wrote: > > MichaelKim wrote: >> Cygwin make always processing `$(chrome_jar_file)` target, after first >> successful build. So I neve

Cygwin make target is never determined up to date

2010-05-04 Thread MichaelKim
Cygwin make always processing `$(chrome_jar_file)` target, after first successful build. So I never get up to date message and always see commands for `$(chrome_jar_file)` are executing. However it happens only on Windows 7. On Windows XP once it built and intact, no more builds. I narrowed down