From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] python-psutil: fix build against musl C library
Date: Tue, 20 Sep 2016 14:38:37 +0200 [thread overview]
Message-ID: <20160920143837.5bed86bd@free-electrons.com> (raw)
In-Reply-To: <87shsu3i2z.fsf@dell.be.48ers.dk>
Hello,
Adding Rich from musl in Cc.
On Tue, 20 Sep 2016 13:51:16 +0200, Peter Korsgaard wrote:
> > The answer of the musl developers would be: don't include
> > <linux/ethtool.h> in the first place.
>
> I don't see the point of that reasoning - The whole idea of the Linux
> uapi headers is to provide headers for the kernel API.
Correct. I've already discussed this with the musl developers, and they
say that the "kernel headers are not clean to be used in userspace".
Of course, everyone else but the musl people are using the uapi headers
in userspace, but apparently, there are some things in there that do
not please the musl people.
Maybe Rich can explain more precisely the issue. So far I've only been
able to get "kernel headers are not clean enough", but not concrete
example of the problem.
> I'm not particulary interested in musl support for
> python-psutil. Alternatively we can just mark it as
> !BR2_TOOLCHAIN_USES_MUSL.
>
> What do you suggest?
I don't care about python-psutil to be available with musl, so your
proposal is fine to me. Overall, I find the policy of musl developers
to be very annoying as:
1/ It breaks many many many packages.
2/ The only proposed solution is to duplicate code, which is not nice
at all, and is difficult to get accepted by upstream project,
living us with zillions of musl-related patches that we cannot
upstream.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-09-20 12:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 7:41 [Buildroot] [PATCH 1/2] python-psutil: bump to version 4.3.1 Peter Korsgaard
2016-09-20 7:41 ` [Buildroot] [PATCH 2/2] python-psutil: fix build against musl C library Peter Korsgaard
2016-09-20 10:14 ` Thomas Petazzoni
2016-09-20 10:30 ` Peter Korsgaard
2016-09-20 11:30 ` Thomas Petazzoni
2016-09-20 11:51 ` Peter Korsgaard
2016-09-20 12:38 ` Thomas Petazzoni [this message]
2016-09-20 13:04 ` Peter Korsgaard
2016-09-20 12:38 ` [Buildroot] [PATCH 1/2] python-psutil: bump to version 4.3.1 Peter Korsgaard
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=20160920143837.5bed86bd@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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