Judging from the outpouring of support I received when I made the same suggestion/offer :-( I'm unsurprised at seeing no public response to yours either. But disappointed. I agree that this is a real problem which does not seem to resonate with those not directly affected by it.
I think the best approach is probably to follow the CVS commit trail, find the commit which fixed the original bug, and see if it can be made conditional on a special target .ALLOW_MIXED_RULES: or something. This could then be requested without any makefile modification by something like export MAKEFLAGS="--eval .ALLOW_MIXED_RULES:" Alternatively, if Paul would allow it, the test could be directly for an EV. The question in my mind, which would probably be answerable by finding the commit, is whether the original fix was a simple patch which could be easily conditionalized or a part of a large-scale parser rewrite. David On Thu, Nov 3, 2011 at 11:54 PM, Jonathan Nieder <invalid.nore...@gnu.org> wrote: > Follow-up Comment #7, bug #33034 (project make): > > Just for the record, I have been looking for a spare moment to come up with a > patch to fix this compatibility problem (which affects many projects other > than the Linux kernel, too). > > If that's a bad idea for some reason, please feel free to let me know why. :) > And if anyone else starts before I do, I won't mind --- on the contrary, I'll > be very happy. > > _______________________________________________________ > > Reply to this item at: > > <http://savannah.gnu.org/bugs/?33034> > > _______________________________________________ > Message sent via/by Savannah > http://savannah.gnu.org/ > > _______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
