From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: iproute2 & other software
Date: Wed, 2 Mar 2016 21:49:41 +0100 [thread overview]
Message-ID: <20160302204941.GH29662@port70.net> (raw)
In-Reply-To: <CAOp4FwSd4bwCadzLnd-0o+v4VBouhH47JMN___xWKQH9O82nyA@mail.gmail.com>
* Loganaden Velvindron <loganaden@gmail.com> [2016-03-02 19:19:13 +0000]:
> "
> Sorry, I have to reject this.
> All include files in include/linux come from headers automatically
> generated from upstream
> Linux source. This is the only way to ensure long term ABI/API consistency
> with kernel.
>
> Either fix musl or submit patches to upstream kernel and get them merged.
> "
>
> Can we look into providing somekind of compatibility layer for header files
> so that it's easier to get upstream projects like iproute2 to support musl ?
>
in theory the correct solution is to fix the kernel headers
so they don't collide with posix types in libc headers.
in practice old kernel headers should work too and it's unlikely
that a complete uapi fix would be accepted into linux any time
soon so applications should avoid including both libc and kernel
headers into the same tu.
unfortunately glibc added workarounds into libc and uapi headers
that make it seem as if mixing linux and libc headers work, so
now application programmers don't have the incentive to fix this.
musl cannot use the same workarounds because they use ifdef __GLIBC__
(which is a major bug for linux uapi headers to depend on):
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/include/uapi/linux/libc-compat.h
next prev parent reply other threads:[~2016-03-02 20:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 19:19 Loganaden Velvindron
2016-03-02 20:37 ` Khem Raj
2016-03-02 20:39 ` Loganaden Velvindron
2016-03-02 20:44 ` Khem Raj
2016-03-02 23:18 ` Rich Felker
2016-03-02 20:49 ` Szabolcs Nagy [this message]
2016-03-02 23:30 ` Rich Felker
2016-03-03 10:10 ` Szabolcs Nagy
2016-03-03 16:00 ` Rich Felker
2016-03-03 16:12 Kylie McClain
2016-03-03 17:01 ` Szabolcs Nagy
2016-03-03 19:05 ` Rich Felker
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=20160302204941.GH29662@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).