Follow-up Comment #4, bug#65273 (group make):

[comment #3 comment #3:]
> It's usually a good idea to check the NEWS file for things that might cause
differences in behavior

Thanks. I'll do that next time first. :)
I grep'd for the error message and found it through git blame so it didn't
take too long.

[comment #3 comment #3:]
> Unfortunately I can't think of a good way to continue to allow this to work,
other than simply disabling the warning by default which I'd really prefer to
not do.

I agree with your preference. The warning seems useful to catch actual bugs.
The Emacs Makefile was just written before it existed.

[comment #3 comment #3:]
> I wonder how common this particular little trick is, out in the world.

I'm surprised no one else has ran into it and reported it since the change is
a year old. I'll submit a bug or email the Emacs people about it later today.
I assume the goal was to make it output in the same way that ./configure
--enable-silent-rules would. Removing the whitespace would cause the output to
look different but would silence the warnings so they aren't interpreted as a
bug like I did. If I manage to think of a decent syntax for adding whitespace
I'll propose it on the mailing list. Thanks for the help! Feel free to mark
this as "Not a bug" if you'd like. I'm not sure how to on Savannah.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?65273>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/


Reply via email to