From: Stephen Hemminger <stephen@networkplumber.org>
To: Felix Janda <felix.janda@posteo.de>
Cc: netdev@vger.kernel.org
Subject: Re: iproute2: Make linux/in6.h a stub?
Date: Mon, 27 Apr 2015 09:17:04 -0700 [thread overview]
Message-ID: <20150427091704.125f42cb@urahara> (raw)
In-Reply-To: <20150425205410.GB9433@euler>
On Sat, 25 Apr 2015 22:54:11 +0200
Felix Janda <felix.janda@posteo.de> wrote:
> Hello.
>
> Background:
> Current iproute2 does not build when the libc is musl instead of glibc.
> This is because of redefinition of in6_addr in netinet/in.h and
> linux/in6.h. There are workarounds in linux/libc-compat.h to make it
> somehow work for glibc.
>
>
> As I can see linux/in6.h is only indirectly used via the other kernel
> headers linux/if_bridge.h and linux/xfrm.h. These in turn include
> linux/in6.h only in order to get a declaration of in6_addr.
>
> Since iproute2 depends on the fact that in6_addr is defined in
> <netinet/in.h> it should be safe to replace the content of linux/in6.h
> by
>
> #include <netinet/in.h>
>
> This completely removes the possibility for redefinition of in6_addr
> for any libc. Since linux/in6.h is anyway a patched kernel header, such
> a change should also not increase the work needed to sync with newer
> kernel headers.
>
> Would it be possible to implement such a change?
>
> Felix
I appreciate the effort to make iproute2 in other environments.
The header files in linux for iproute2 are automatically generated
from the upstream kernel headers. A lot of effort has been done
to align kernel, iproute2 and glibc. Therefore doing something
special just to work around incompatibles with other
environments is not going to be accepted.
Any other libc has to be compatible with glibc in this area
rather than introducing more complexity in what is already fragile.
next prev parent reply other threads:[~2015-04-27 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-25 20:54 iproute2: Make linux/in6.h a stub? Felix Janda
2015-04-27 16:17 ` Stephen Hemminger [this message]
2015-04-29 17:36 ` Felix Janda
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=20150427091704.125f42cb@urahara \
--to=stephen@networkplumber.org \
--cc=felix.janda@posteo.de \
--cc=netdev@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