Re: Lintian warning: hardening-no-fortify-functions & version numbering
"Bernhard R. Link" <email@example.com> writes:
> * Lars Wirzenius <firstname.lastname@example.org> [120624 12:30]:
>> On Sat, Jun 23, 2012 at 03:27:07PM -0700, Russ Allbery wrote:
>>> CFLAGS is an old, long-standing make thing. CPPFLAGS is newer and I
>>> believe was introduced by Autoconf
>> I don't know the history of CPPFLAGS. It's possible it was introduced by
>> Autoconf. However, it is now embedded into the implicit rules of GNU Make,
>> so every Makefile that doesn't override the rule for compiling a .c file
>> to a .o file uses CPPFLAGS.
> Where "now" means since 1990.
Yeah. I think CFLAGS may be another 10-15 years older, but I haven't done
the research. Anyway, this is the way that all Autoconf and Automake
software works, which gets quite a lot of free software, and while I'm not
sure whether any possible preprocessor flags we might want to add in the
future would affect cpp-only tests, I wouldn't want to rule it out.
When integrating with a build system that uses only one variable for
compilation flags, just pass the concatenation of CFLAGS and CPPFLAGS into
it. This is trivially done in debian/rules without modifying the upstream
Russ Allbery (email@example.com) <http://www.eyrie.org/~eagle/>