author | Florian Forster <octo@leeloo.lan.home.verplant.org> | |
Thu, 17 Sep 2009 06:44:07 +0000 (08:44 +0200) | ||
committer | Florian Forster <octo@leeloo.lan.home.verplant.org> | |
Thu, 17 Sep 2009 06:44:07 +0000 (08:44 +0200) | ||
commit | a690e4ac74e05f7294c22df8e0574e5e6f52f510 | |
tree | 2ae66d1950c340888d3e0a1c872742ddaf7b22e7 | tree | snapshot |
parent | 81207a4725755b4df70c2d329225f118475f0253 | commit | diff |
Build system: Improve detection of the iptc library.
When checking for the iptc headers and data types, the configure script
added the kernel directory to the CFLAGS. Later, when actually building
the iptables plugin, the CFLAGS were left untouched.
At least on Debian, the “real” kernel headers are not required – the
libc versions in /usr/include/linux are sufficient. The usage of
KERNEL_DIR has therefore been removed from the iptc checks.
In addition, an directory specified by “--with-libiptc=/path” is no
longer added to the global CFLAGS but rather to the iptables specific
CPPFLAGS.
Hopefully this resolved build problems on various platforms.
When checking for the iptc headers and data types, the configure script
added the kernel directory to the CFLAGS. Later, when actually building
the iptables plugin, the CFLAGS were left untouched.
At least on Debian, the “real” kernel headers are not required – the
libc versions in /usr/include/linux are sufficient. The usage of
KERNEL_DIR has therefore been removed from the iptc checks.
In addition, an directory specified by “--with-libiptc=/path” is no
longer added to the global CFLAGS but rather to the iptables specific
CPPFLAGS.
Hopefully this resolved build problems on various platforms.
configure.in | diff | blob | history | |
src/Makefile.am | diff | blob | history |