From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] freerdp: fix build with uclibc snapshot and uclibc-ng
Date: Wed, 29 Apr 2015 09:29:34 +0200 [thread overview]
Message-ID: <20150429092934.31ea503b@free-electrons.com> (raw)
In-Reply-To: <XnsA48AE66F8143FberndkuhlsPkbjNfxxIA@bernd-kuhls.de>
Dear Bernd Kuhls,
On Tue, 28 Apr 2015 22:39:10 +0200, Bernd Kuhls wrote:
> what about adding eventfd_read() and eventfd_write() to
> package/uclibc/0.9.33.2/? This function is needed by upcoming Kodi 15.0
> Isengard as well and will be part[1] of my next RFC-patch series when beta1
> of the next Kodi version will be released.
Once again, the issue with this approach is that it simply does work
for external uClibc toolchains. Such toolchains will not have all the
feature patches that Buildroot has, so packages will fail to build with
such external uClibc toolchains.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-04-29 7:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 19:40 [Buildroot] [PATCH] freerdp: fix build with uclibc snapshot and uclibc-ng Baruch Siach
2015-04-28 20:39 ` Bernd Kuhls
2015-04-29 4:30 ` Baruch Siach
2015-04-29 7:29 ` Thomas Petazzoni [this message]
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=20150429092934.31ea503b@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