From: Phil Sutter <phil@nwl.cc>
To: Alyssa Ross <hi@alyssa.is>
Cc: netfilter-devel@vger.kernel.org, Joshua Lant <joshualant@googlemail.com>
Subject: Re: [PATCH nftables] include: fix for musl with iptables v1.8.11
Date: Fri, 20 Dec 2024 12:50:42 +0100 [thread overview]
Message-ID: <Z2VaEv0u3ZPcWqye@orbyte.nwl.cc> (raw)
In-Reply-To: <20241219231001.1166085-2-hi@alyssa.is>
Hi Alyssa,
On Fri, Dec 20, 2024 at 12:10:02AM +0100, Alyssa Ross wrote:
> Since iptables commit 810f8568 (libxtables: xtoptions: Implement
> XTTYPE_ETHERMACMASK), nftables failed to build for musl libc:
>
> In file included from /nix/store/bvffdqfhyxvx66bqlqqdmjmkyklkafv6-musl-1.2.5-dev/include/netinet/et…
> from /nix/store/kz6fymqpgbrj6330s6wv4idcf9pwsqs4-iptables-1.8.10-de…
> from src/xt.c:30:
> /nix/store/bvffdqfhyxvx66bqlqqdmjmkyklkafv6-musl-1.2.5-dev/include/netinet/if_ether.h:115:8: error: redefinition of 'struct ethhdr'
> 115 | struct ethhdr {
> | ^~~~~~
> In file included from ./include/linux/netfilter_bridge.h:8,
> from ./include/linux/netfilter_bridge/ebtables.h:1,
> from src/xt.c:27:
> /nix/store/bvffdqfhyxvx66bqlqqdmjmkyklkafv6-musl-1.2.5-dev/include/linux/if_ether.h:173:8: note: originally defined here
> 173 | struct ethhdr {
> | ^~~~~~
>
> The fix is to use libc's version of if_ether.h before any kernel
> headers, which takes care of conflicts with the kernel's struct ethhdr
> definition by defining __UAPI_DEF_ETHHDR, which will tell the kernel's
> header not to define its own version.
What I don't like about this is how musl tries to force projects to not
include linux/if_ether.h directly. From the project's view, this is a
workaround not a fix.
> Signed-off-by: Alyssa Ross <hi@alyssa.is>
> ---
> A similar fix would solve the problem properly in iptables, which was
> worked around with 76fce228 ("configure: Determine if musl is used for build").
> The __UAPI_DEF_ETHHDR is supposed to be set by netinet/if_ether.h,
> rather than manually by users.
Why does 76fce228 not work for you?
Cheers, Phil
next prev parent reply other threads:[~2024-12-20 11:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 23:10 [PATCH nftables] include: fix for musl with iptables v1.8.11 Alyssa Ross
2024-12-20 11:50 ` Phil Sutter [this message]
2024-12-20 12:07 ` Alyssa Ross
2024-12-20 12:33 ` Phil Sutter
2024-12-21 15:34 ` Alyssa Ross
2025-01-08 23:34 ` Pablo Neira Ayuso
2025-01-08 23:49 ` Phil Sutter
2025-01-09 0:03 ` Pablo Neira Ayuso
2025-01-09 10:02 ` Phil Sutter
2026-02-11 13:49 ` Florian Westphal
2026-02-11 18:59 ` Phil Sutter
2026-02-11 19:09 ` Florian Westphal
2026-02-11 20:19 ` Phil Sutter
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=Z2VaEv0u3ZPcWqye@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=hi@alyssa.is \
--cc=joshualant@googlemail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.