[bug #46242] Race condition when input file is updated while compiling

Update of bug #46242 (project make): Item Group: Bug => Enhancement ___ Reply to this item at: ___ Messag

Re: [bug #46242] Race condition when input file is updated while compiling

Hi, > However, the main concern with either approach [...] many complications and > corner cases, some as noted by Reiner Post. I'm curious and will check these out at some point. > I think you’re missing the fact that nobody is actually working on > these things. Make is an open-source project

Re: [bug #46242] Race condition when input file is updated while compiling

On Wed, Oct 21, 2015 at 1:01 AM, Egmont Koblinger wrote: > Is there any realistic ETA on this feature? I think you’re missing the fact that nobody is actually working on these things. Make is an open-source project and not one of the ones that has direct corporate backing or engineers paid to wor

Re: [bug #46242] Race condition when input file is updated while compiling

On Tue, Oct 20, 2015 at 2:07 PM, Mike Shal wrote: > I would clarify that the benefit from using the technique in that article is > really because the rebuild algorithm is essentially changed from: > > if timestamp(foo.o) < timestamp(foo.c) {rebuild foo.o} > > to: > > if checksum(foo.c) != last_che

Re: [bug #46242] Race condition when input file is updated while compiling

On Tue, Oct 20, 2015 at 11:07 PM, Mike Shal wrote: if timestamp(foo.o) < timestamp(foo.c) {rebuild foo.o} > > to: > > if checksum(foo.c) != last_checksum(foo.c) {rebuild things that depend on > foo.c} > > But you can get pretty much all the same benefits without having to hash > everything just b

Re: [bug #46242] Race condition when input file is updated while compiling

On Tue Oct 20 20:36:13 2015, egm...@gmail.com (Egmont Koblinger) wrote: [...] > > I don't think make should be worried about this potential race; it's an > > obvious case of user error with an easy discipline for the user to apply > > to avoid any problems. > > Is it really obvious? Is it docum

Re: [bug #46242] Race condition when input file is updated while compiling

On Tue, Oct 20, 2015 at 3:57 PM, David Boyce wrote: > My view is that this is really a variant of the longstanding > discussion about getting make to not rely on timestamps at all and use > MD5 or similar digital signatures instead. There are a number of > reasons why timestamps can be insufficie

Re: [bug #46242] Race condition when input file is updated while compiling

This is mixing up two things. The article discusses ways of doing this at the makefile level, i.e. without any mods needed to make per se. There’s also a separate longstanding discussion with multiple proposals for how to modify make to add a native checksum capability. David On Tue, Oct 20, 2015

Re: [bug #46242] Race condition when input file is updated while compiling

This sounds like an awesome idea! The article being 9 years old makes me wonder though... is it something that'll be done in the foreseeable future? thx, e. On Tue, Oct 20, 2015 at 9:57 PM, David Boyce wrote: > My view is that this is really a variant of the longstanding > discussion about get

Re: [bug #46242] Race condition when input file is updated while compiling

My view is that this is really a variant of the longstanding discussion about getting make to not rely on timestamps at all and use MD5 or similar digital signatures instead. There are a number of reasons why timestamps can be insufficient beside this race condition, so I think it might be better t

Re: [bug #46242] Race condition when input file is updated while compiling

Hi, Let me tell 2 real-life examples: 1. The one that made me find this issue: My hobby project takes 45 seconds to compile, out of which the biggest .cc file that I modify most of the time is 15 seconds. In order to understand what's going on (it was not written by me, I'm just fixing bugs and

Re: [bug #46242] Race condition when input file is updated while compiling

> There's an inherent race condition in the way "make" handles timestamps. If > you save a newer version of a file while make is running and is just compiling > that input file, the change won't be picked up by subsequent runs of "make", > and you'll be left with an out-of-date binary. The traditi

[bug #46242] Race condition when input file is updated while compiling

Follow-up Comment #1, bug #46242 (project make): Clarification: 7. Go back to the terminal. make might have completed by now. If not, you might either -- if it has finished processing that file and is already working on another -- interrupt it, or wait for it to complete. ___

[bug #46242] Race condition when input file is updated while compiling

URL: Summary: Race condition when input file is updated while compiling Project: make Submitted by: egmont Submitted on: Sun 18 Oct 2015 05:28:22 PM GMT Severity: 3 - Normal