[bug #52912] minor bug in GNU make's own Makefile under .ONESHELL

Follow-up Comment #4, bug #52912 (project make): Yes, I understand you weren't suggesting the fake "bash" be on PATH. But I still think it's an unfortunate hack. I've been using the build of make itself as a test/demo for a related build tool I'm working on. I'm under no illusion that the rest of

[bug #52912] minor bug in GNU make's own Makefile under .ONESHELL

Update of bug #52912 (project make): Status:None => Wont Fix Open/Closed:Open => Closed ___ Follow-up Comment #3: I'm saying that if you

[bug #52912] minor bug in GNU make's own Makefile under .ONESHELL

Follow-up Comment #2, bug #52912 (project make): Hmm. When you say "I think that your use-case is going to cause lots of other problems", I'm not sure whether you're referring to the make build model per se or the greater universe of makefiles. I'm aware that .ONESHELL has certain pitfalls in the

[bug #52912] minor bug in GNU make's own Makefile under .ONESHELL

Follow-up Comment #1, bug #52912 (project make): Unfortunately, Makefile.in is generated by automake and that rule is part of automake's autogenerated content, it's not part of GNU make, so there's not much we can do about it (at least, not easily). I think that your use-case is going to cause lo

[bug #52912] minor bug in GNU make's own Makefile under .ONESHELL

URL: Summary: minor bug in GNU make's own Makefile under .ONESHELL Project: make Submitted by: boyski Submitted on: Tue 16 Jan 2018 02:12:06 PM UTC Severity: 3 - Normal I