This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Cygwin make target is never determined up to date
MichaelKim wrote:
> Yea I tried to add sleep, no good. Consequent calls doesn't go
> $(jar_target_dir) target, they only run $(chrome_jar_file) target.
>
> It's NTFS, Windows 7. The other system which performs as expected Windows
> XP, again NTFS.
> Here is some additional information:
>
> Reading makefiles...
> Updating goal targets....
> File `all' does not exist.
> Prerequisite `../bin/build/chrome' is newer than
> target `../bin/build/chrome/alt.jar'.
> Must remake target `../bin/build/chrome/alt.jar'.
> Creating chrome JAR file.
> updating: content/about.js (deflated 66%)
> updating: content/sprintf.js (deflated 52%)
> ...
>
> and stats
>
> $ stat ../bin/build/chrome/alt.jar ../bin/build/chrome
> File: `../bin/build/chrome/alt.jar'
> Size: 29220 Blocks: 32 IO Block: 65536 regular file
> Device: 22c6affh/36465407d Inode: 59672695062724268 Links: 1
> Access: (0644/-rw-r--r--) Uid: ( 1000/ xxx) Gid: ( 513/ None)
> Access: 2010-05-05 13:03:01.066457300 +0900
> Modify: 2010-05-05 13:03:01.088960100 +0900
> Change: 2010-05-05 13:03:01.091460400 +0900
> File: `../bin/build/chrome'
> Size: 0 Blocks: 0 IO Block: 65536 directory
> Device: 22c6affh/36465407d Inode: 3940649674014457 Links: 1
> Access: (0755/drwxr-xr-x) Uid: ( 1000/ xxx) Gid: ( 513/ None)
> Access: 2010-05-05 13:03:01.090960400 +0900
> Modify: 2010-05-05 13: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`
So let me get this straight. The JAR file you're trying to build is
within a directory which is listed as a prerequisite of that JAR file?
Unless I'm completely off base, it would seem to be that this is
expected behavior then. If you mess with the contents of a directory,
such as by adding a file to it, the last modified timestamp of the
directory is going to be updated. I would expect that to happen after
the file is added to the directory which could very well be *after* the
last modified timestamp of the file is set. Thus the directory will
appear newer than the file.
I can't explain why this works for you under XP, but I don't think this
is Cygwin's doing. Cygwin is most likely just letting the filesystem do
its thing without interference.
-Jeremy
--
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