From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Baruch Siach <baruch@tkos.co.il>
Cc: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org
Subject: Re: [PATCH iptables] utils: nfsynproxy: fix build with musl libc
Date: Fri, 3 Mar 2017 10:55:26 +0100 [thread overview]
Message-ID: <20170303095526.GA11571@salvia> (raw)
In-Reply-To: <06e0312d0bfd1f0b9e7c23ab654f18524d49e86b.1488440107.git.baruch@tkos.co.il>
On Thu, Mar 02, 2017 at 09:35:07AM +0200, Baruch Siach wrote:
> The musl libc exposes some struct tcphdr field only when _GNU_SOURCE is
> defined. Fix the following build failure:
>
> nfsynproxy.c: In function ‘parse_packet’:
> nfsynproxy.c:34:9: error: ‘const struct tcphdr’ has no member named ‘syn’
> if (!th->syn || !th->ack)
> ^
> nfsynproxy.c:34:21: error: ‘const struct tcphdr’ has no member named ‘ack’
> if (!th->syn || !th->ack)
> ^
> nfsynproxy.c:42:8: error: ‘const struct tcphdr’ has no member named ‘res2’
> if (th->res2 == 0x1)
> ^
> nfsynproxy.c:45:13: error: ‘const struct tcphdr’ has no member named ‘doff’
> length = th->doff * 4 - sizeof(*th);
> ^
Applied, thanks.
prev parent reply other threads:[~2017-03-03 15:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 7:35 [PATCH iptables] utils: nfsynproxy: fix build with musl libc Baruch Siach
2017-03-03 9:55 ` Pablo Neira Ayuso [this message]
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=20170303095526.GA11571@salvia \
--to=pablo@netfilter.org \
--cc=baruch@tkos.co.il \
--cc=coreteam@netfilter.org \
--cc=kadlec@blackhole.kfki.hu \
--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).