Wireshark mailing list archives
Re: When did autotools started to use AM_CPPFLAGS
From: David Arnold <davida () pobox com>
Date: Mon, 11 Mar 2013 12:00:36 +0100
On 11/03/2013, at 8:10 AM, Jaap Keuter wrote: Hi Jaap,
ref bug 8452. When did autotools started to use AM_CPPFLAGS, which are now favorable over INCLUDE? Do we break anything with this cleanup?
(I submitted the bug) The automake documentation says: INCLUDES This does the same job as AM_CPPFLAGS (or any per-target _CPPFLAGS variable if it is used). It is an older name for the same functionality. This variable is deprecated; we suggest using AM_CPPFLAGS and per-target _CPPFLAGS instead. On that basis, I believe they're synonyms, and the automake folks are pushing everyone towards the AM_* style variables. I see the annoying logspew using OSX with MacPorts and automake-1.13.1 (and I *think* on Debian/testing as well, but that box is inaccessible right now, so I cannot confirm that). I've updated the bug, d ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- When did autotools started to use AM_CPPFLAGS Jaap Keuter (Mar 11)
- Re: When did autotools started to use AM_CPPFLAGS David Arnold (Mar 11)
- Re: When did autotools started to use AM_CPPFLAGS Jaap Keuter (Mar 11)
- Re: When did autotools started to use AM_CPPFLAGS David Arnold (Mar 11)
- Re: When did autotools started to use AM_CPPFLAGS Jaap Keuter (Mar 11)
- Re: When did autotools started to use AM_CPPFLAGS Jaap Keuter (Mar 11)
- Re: When did autotools started to use AM_CPPFLAGS David Arnold (Mar 11)