Jonas Berlin notes that --with-xtables only emitted a -I parameter
and -L was absent.
On second look, we would also be missing -Wl,-rpath, and that would
all be system-dependent. The --with-xtables option is actually not
needed; one can easily specify extra include directories and linker
flags by means of overriding libxtables_CFLAGS and libxtables_LIBS
(even when there are no installed pkgconfig files for libxtables).
Because we are likely to be having more userspace programs soon, and
reproducing manual makefiles is a bad idea, make extensions/ ready
for automake traversal. The build pattern now is:
1. toplevel Makefile.am starts off with extensions/Makefile.am
2. Makefile.am
a. builds programs in current directory
b. runs Kbuild
- only from extensions/Makefile.am
(so it does not get reinvoked from case 2cII)
- Kbuild recurses on its own
c. runs Mbuild
I. builds iptables shared libraries in current directory
II. runs Makefile.am in each subdir (goto step 2.)
The prototype of ip_route_me_harder changed in 2.6.18.5, so I think
Xtables-addons should account for it. This renders compilation on
anything below it impossible. (2.6.17 is not supported in general.)
Some code already uses ip_hdr() functions which did not exist in
2.6.21 and I do not feel like adding more compat code.
Signed-off-by: Jan Engelhardt <jengelh@computergmbh.de>
The extension modules use the API of a fairly recent kernel, if not
even the networking git tree. To make it work with older Linux
kernels, an API wrapper is added. Should compile against
running-kernels Linux 2.6.19..current (tested: 2.6.22..current).
Signed-off-by: Jan Engelhardt <jengelh@computergmbh.de>
Populate the iptables-addons repository with two modules, xt_TARPIT
and xt_TEE, as a starting point.
Signed-off-by: Jan Engelhardt <jengelh@computergmbh.de>
