[bug #20394] vpath directive drops entries

Update of bug #20394 (project make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Fixed Release:

[bug #20394] vpath directive drops entries

Follow-up Comment #7, bug #20394 (project make): As to when to use the cache vs. avoid it, I actually meant the opposite from what you wrote. Maybe it's more clear with a practical example: $ time make -C fltk-1.1.7, up-to-date, on a (slow) Ubuntu box: make (3.81b4, as is): - 3.8 sec make (cvs,

[bug #20394] vpath directive drops entries

Follow-up Comment #6, bug #20394 (project make): I haven't looked into it carefully, but it's not immediately clear to me that it's a simple thing to avoid the directory cache for chained/intermediate rules, vs. any other kind of rule. The disadvantage with the "is_stale" boolean is that every t

[bug #20394] vpath directive drops entries

Follow-up Comment #5, bug #20394 (project make): Timestamps are a different matter, gmake doesn't use the cache to check timestamps of files. Also, what I meant was *chained* rules with intermediate files, not first-level implicit rules. Basically it is so that gmakes spends all win from the cach

[bug #20394] vpath directive drops entries

Follow-up Comment #4, bug #20394 (project make): Something like that could be tricky to accomplish, since make is highly recursive: when make starts checking for timestamps on files it doesn't know whether that file was found using implicit or explicit rules, etc. Plus, I think it would be even

[bug #20394] vpath directive drops entries

Follow-up Comment #3, bug #20394 (project make): It would maybe make sense to rely on the directory cache only for intermediate search and match-anything rules. Because these two alone increase the number of file-queries by a factor of about 10. That is just from the 5 built-in rules (which moreo

[bug #20394] vpath directive drops entries

Follow-up Comment #2, bug #20394 (project make): It's not exactly correct to say that GNU make caches directories from the 10th on, but you're on exactly the right track; thanks for the note. What make actually does is cache EVERY directory... BUT it caches them "lazily", AND it only allows 10 d

[bug #20394] vpath directive drops entries

Follow-up Comment #1, bug #20394 (project make): gmake caches directories from the 10th on. So it will not see a file in those directories if it didn't exist initially (except under windows NT, where it checks the directory timestamps). Just looks like foo1..8 plus lib, include and . were one m

[bug #20394] vpath directive drops entries

URL: Summary: vpath directive drops entries Project: make Submitted by: None Submitted on: Samstag 07.07.2007 um 08:09 UTC Severity: 3 - Normal Item Group: Bug