From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: Felix Janda <felix.janda@posteo.de>, netfilter-devel@vger.kernel.org
Subject: Re: [iptables PATCH 2/2 RFC] Remove Libc5 support code
Date: Mon, 4 May 2015 12:55:43 +0200 [thread overview]
Message-ID: <20150504105543.GA3622@salvia> (raw)
In-Reply-To: <20150504104809.GH22481@breakpoint.cc>
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.
next prev parent reply other threads:[~2015-05-04 10:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-02 19:51 [iptables PATCH 2/2 RFC] Remove Libc5 support code Felix Janda
2015-05-04 10:48 ` Florian Westphal
2015-05-04 10:55 ` Pablo Neira Ayuso [this message]
2015-05-04 11:34 ` Jozsef Kadlecsik
2015-05-08 14:04 ` Florian Westphal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150504105543.GA3622@salvia \
--to=pablo@netfilter.org \
--cc=felix.janda@posteo.de \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).