From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] acpid: unavailable for external uClibc toolchains
Date: Fri, 25 Apr 2014 09:38:02 +0200 [thread overview]
Message-ID: <20140425093802.7c4c90da@skate> (raw)
In-Reply-To: <20140424204218.2F6159C9B8@busybox.osuosl.org>
Dear Peter Korsgaard,
On Thu, 24 Apr 2014 22:35:33 +0200, Peter Korsgaard wrote:
> commit: http://git.buildroot.net/buildroot/commit/?id=ec6aaa4706d6826aca4e48ea65bbebbd893f76d6
> branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
>
> External non-patched uClibc toolchains lack the MSG_CMSG_CLOEXEC
> definition, so does internal uClibc <0.9.33, so exclude it for those
> scenarios. Fixes:
> http://autobuild.buildroot.net/results/6d4/6d471942788fa05f324649ab15e6ca382e46df9c/
Huh? This build failure is due to a difference between a patched
version of uClibc (available in the internal toolchain backend) and an
external uClibc toolchain. Haven't we said that we shouldn't really on
our uClibc internal toolchain having feature patches, and instead patch
the packages?
I'm sorry, but I disagree with the solution chosen here.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-04-25 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 20:35 [Buildroot] [git commit] acpid: unavailable for external uClibc toolchains Peter Korsgaard
2014-04-25 7:38 ` Thomas Petazzoni [this message]
2014-04-25 7:56 ` 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=20140425093802.7c4c90da@skate \
--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