bug#35526: misleading documentation about flag variable ordering

2019-05-01 Thread Daniel Kahn Gillmor
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 compil

bug#35526: misleading documentation about flag variable ordering

2019-05-01 Thread Nick Bowler
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 sa

bug#35526: misleading documentation about flag variable ordering

2019-05-01 Thread Daniel Kahn Gillmor
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 *