Back on this bug from May 2019 (https://bugs.gnu.org/35526).
Sorry for the delay.
The implication here is that for any of the *FLAGS variables, later
options are inherently more effective than earlier options.
This is not the case universally.
Granted. After reading the messages
On Wed 2019-05-01 14:28:01 -0400, Nick Bowler wrote:
> On 5/1/19, Daniel Kahn Gillmor wrote:
>> https://www.gnu.org/software/automake/manual/automake.html#Flag-Variables-Ordering
>> says:
>>
>> The reason ‘$(CPPFLAGS)’ appears after ‘$(AM_CPPFLAGS)’ or
>> ‘$(mumble_CPPFLAGS)’ in the
On 5/1/19, Daniel Kahn Gillmor wrote:
> https://www.gnu.org/software/automake/manual/automake.html#Flag-Variables-Ordering
> says:
>
> The reason ‘$(CPPFLAGS)’ appears after ‘$(AM_CPPFLAGS)’ or
> ‘$(mumble_CPPFLAGS)’ in the compile command is that users should
> always have the last
https://www.gnu.org/software/automake/manual/automake.html#Flag-Variables-Ordering
says:
The reason ‘$(CPPFLAGS)’ appears after ‘$(AM_CPPFLAGS)’ or
‘$(mumble_CPPFLAGS)’ in the compile command is that users should
always have the last say.
The implication here is that for any of the
