From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] autobuild - acpid does not build against musl
Date: Tue, 21 Jul 2015 09:26:27 +0200 [thread overview]
Message-ID: <20150721092627.0fa306db@free-electrons.com> (raw)
In-Reply-To: <CA+BsyQ7vZTqjt9OKgj_tcBTx=rC9zHCxzmN4wSPJ=20TD=MRwA@mail.gmail.com>
Brendan,
On Tue, 21 Jul 2015 01:16:16 +0100, Brendan Heading wrote:
> I think the best course with this problem is to have a chat with the
> upstream musl guys (first choice) or patch the buildroot musl
> toolchain (second choice).
Neither of this is going to happen, I believe. TEMP_FAILURE_RETRY is a
glibc-ism, and the musl developers are generally not really interested
in adding glibc-isms.
Patching the buildroot musl toolchain is also not acceptable, as it
means we would no longer support musl external toolchains that don't
carry our patches.
> The absence of TEMP_FAILURE_RETRY will break more than one package so
> in retrospect it's probably more cleaner to try to fix it properly
> rather than add patches to every package where it shows up. The only
> downside is that acpid will be broken until it's resolved.
But that's still the only reasonable solution. The idea being that
those patches should be contributed to the upstream acpid project, so
that we can drop them from Buildroot the next time acpid makes an
official release.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-07-21 7:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 18:35 [Buildroot] [PATCH] autobuild - acpid does not build against musl Brendan Heading
2015-07-20 18:52 ` Baruch Siach
2015-07-20 19:15 ` Brendan Heading
2015-07-20 20:41 ` Thomas Petazzoni
2015-07-21 0:16 ` Brendan Heading
2015-07-21 7:26 ` Thomas Petazzoni [this message]
2015-07-21 12:15 ` Brendan Heading
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=20150721092627.0fa306db@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