Bug 155406
Summary: | make thinks file is out of date if it has the same modification time as prerequisite | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Andrew Schultz <ajschult784> |
Component: | kernel | Assignee: | Stephen Tweedie <sct> |
Status: | CLOSED DUPLICATE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | davej |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-30 15:38:07 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Andrew Schultz
2005-04-20 03:51:41 UTC
What filesystem is this on? I certainly can't reproduce this on ext3: touch foo; make; make; make cp -p foo bar make: `bar' is up to date. make: `bar' is up to date. I was testing this on ext3 for FC3 and RHEL4. I retested on FC3 now and it's working. The only thing I can think of that would have fixed this was a kernel upgrade (2.6.10-1.770_FC3 => 2.6.11-1.14_FC3). RHEL4 with 2.6.9-5.0.5 is still a problem. If that depends on the exact kernel, then it is a kernel issue, not a make one. The reason the kernel is implicated is that RHEL-4 GA kernel honours sub-microsecond timestamp updates on ext3 in memory (though not on disk.) Upstream has disabled that, and this has been back-ported to RHEL-4 for U2. I can reproduce this on RHEL-4 GA but not on the U2 kernel, so I'm closing this as a dup. Note that this problem still occurs even on U2 if you use the tmpfs filesystem, as that does have true nanosecond timestamp support; cp -p only updates the microsecond, but not nanosecond, component (because of the utimes(2) granularity limit), and it doesn't round, so drops the lower 3 decimal digits of the nanosecond cound. If this is still a problem, please reopen against coreutils. *** This bug has been marked as a duplicate of 145976 *** |