Jan Ziak (12 April 2017 20:07)
> Is this a make-4.2.1 bug, or a gcc-6.3.0 bug? The line numbers in the garbled
> error messages, in this case 79 and 84, are correct.
Given its sensitivity to the specific flags passed to gcc, it's natural
to suppose it's a gcc bug. You can test by running gcc manually,
instead of via make; find the rule that's running gcc, remove @ from the
start of its line if present, run make to see the command it invokes;
invoke that command yourself. If the issue arises then, it's definitely
gcc.
Eddy.
_______________________________________________
Bug-make mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-make
