[iptables,2/2,RFC] Remove Libc5 support code

Current code makes the assumption that !defined(__GLIBC__) means libc5
which is very unlikely the case nowadays.

Fixes compile error because of conflict between kernel and musl headers.
---
If libc5 is considered still relevant, I could try to come up with an
autoconf test.
---
 include/libiptc/ipt_kernel_headers.h | 12 ------------
 1 file changed, 12 deletions(-)

Felix Janda <felix.janda@posteo.de> wrote:
> Current code makes the assumption that !defined(__GLIBC__) means libc5
> which is very unlikely the case nowadays.
> 
> Fixes compile error because of conflict between kernel and musl headers.
> ---
> If libc5 is considered still relevant, I could try to come up with an
> autoconf test.

I'm all for removing libc5 support if this is whats preventing iptables
to be built with current non-glibc systems.

Pablo, Patrick, Eric, Jozsef - whats your take on this?
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

On Mon, May 04, 2015 at 12:48:09PM +0200, Florian Westphal wrote:
> Felix Janda <felix.janda@posteo.de> wrote:
> > Current code makes the assumption that !defined(__GLIBC__) means libc5
> > which is very unlikely the case nowadays.
> > 
> > Fixes compile error because of conflict between kernel and musl headers.
> > ---
> > If libc5 is considered still relevant, I could try to come up with an
> > autoconf test.
> 
> I'm all for removing libc5 support if this is whats preventing iptables
> to be built with current non-glibc systems.
> 
> Pablo, Patrick, Eric, Jozsef - whats your take on this?

I would say, go take it.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

On Mon, 4 May 2015, Pablo Neira Ayuso wrote:

> On Mon, May 04, 2015 at 12:48:09PM +0200, Florian Westphal wrote:
> > Felix Janda <felix.janda@posteo.de> wrote:
> > > Current code makes the assumption that !defined(__GLIBC__) means libc5
> > > which is very unlikely the case nowadays.
> > > 
> > > Fixes compile error because of conflict between kernel and musl headers.
> > > ---
> > > If libc5 is considered still relevant, I could try to come up with an
> > > autoconf test.
> > 
> > I'm all for removing libc5 support if this is whats preventing iptables
> > to be built with current non-glibc systems.
> > 
> > Pablo, Patrick, Eric, Jozsef - whats your take on this?
> 
> I would say, go take it.

I second that.

Best regards,
Jozsef
-
E-mail  : kadlec@blackhole.kfki.hu, kadlecsik.jozsef@wigner.mta.hu
PGP key : http://www.kfki.hu/~kadlec/pgp_public_key.txt
Address : Wigner Research Centre for Physics, Hungarian Academy of Sciences
          H-1525 Budapest 114, POB. 49, Hungary
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Jozsef Kadlecsik <kadlec@blackhole.kfki.hu> wrote:
> > On Mon, May 04, 2015 at 12:48:09PM +0200, Florian Westphal wrote:
> > > Felix Janda <felix.janda@posteo.de> wrote:
> > > > Current code makes the assumption that !defined(__GLIBC__) means libc5
> > > > which is very unlikely the case nowadays.
> > > > 
> > > > Fixes compile error because of conflict between kernel and musl headers.
> > > > ---
> > > > If libc5 is considered still relevant, I could try to come up with an
> > > > autoconf test.
> > > 
> > > I'm all for removing libc5 support if this is whats preventing iptables
> > > to be built with current non-glibc systems.
> > > 
> > > Pablo, Patrick, Eric, Jozsef - whats your take on this?
> > 
> > I would say, go take it.
> 
> I second that.

I've applied this patch, thanks everyone.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html