Make loading of static extensions optional to support vanilla iptables
in it's default configuration by setting DISABLE_STATIC_EXTENSIONS
instead of hackery.
In case iptables is built with --disable-static libext.a, libext4.a and
libext6.a which OpenWrt installs in the form of libiptext.so,
The conflict between Musls net/if.h and linux/if.h is an old well known
one and taken care of by a series of linux-headers patches in OpenWrt.
Since Linux 4.8-rc5 Firewall3 also indirectly pulls in linux/in.h and
linux/in6.h leading to new conflicts.
As Firewall3 is fine with just the libc
* Ralph Sennhauser [2016-11-06 10:59:43 +0100]:
> The conflict between Musls net/if.h and linux/if.h is an old well known
> one and taken care of by a series of linux-headers patches in OpenWrt.
> Since Linux 4.8-rc5 Firewall3 also indirectly pulls in linux/in.h and
>
Hi again,
> Will see if I find another solution...
I managed to find a solution that works for me on a Linux 4.6.0 system
with glibc, a Linux 4.6.0 system with unpatched musl and a Linux 4.4
system with patched kernel headers.
I pushed this change along with a few others that should aid in
Hi Ralph,
I took the CMakeLists.txt change as-is but modified the rest to use
no-op declarations of init_extensions{,4,6}() in order to avoid
sprinkling too much ifdefs around.
Thanks,
Jo
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Hi Ralph,
unfortunately this breaks building on a glibc system for me:
-- 8< --
$ make
[ 7%] Building C object CMakeFiles/firewall3.dir/iptables.c.o
In file included from /usr/include/linux/netfilter_ipv4.h:8:0,
from /usr/include/linux/netfilter_ipv4/ip_tables.h:21,
Hi Jo
On Sun, 6 Nov 2016 20:48:58 +0100
Jo-Philipp Wich wrote:
> Hi again,
>
> > Will see if I find another solution...
>
> I managed to find a solution that works for me on a Linux 4.6.0 system
> with glibc, a Linux 4.6.0 system with unpatched musl and a Linux 4.4
> system
On Sun, 6 Nov 2016 19:07:01 +0100
Szabolcs Nagy wrote:
> * Ralph Sennhauser [2016-11-06 10:59:43
> +0100]:
> > The conflict between Musls net/if.h and linux/if.h is an old well
> > known one and taken care of by a series of linux-headers patches in
>