Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] freerdp: fix build with uclibc snapshot and uclibc-ng
Date: Fri, 1 May 2015 10:17:30 +0200	[thread overview]
Message-ID: <20150501101730.457d4126@free-electrons.com> (raw)
In-Reply-To: <f32b411ce05373bca0ae48db848f28ab5acafb62.1430451363.git.baruch@tkos.co.il>

Dear Baruch Siach,

On Fri,  1 May 2015 06:36:03 +0300, Baruch Siach wrote:
> uclibc snapshot and uclibc-ng add support for the eventfd_{read,write} glibc
> extensions. Refine our uClibc support patch to take this into account, based
> on upstream fix applied to freerdp master branch.
> 
> Fixes:
> http://autobuild.buildroot.net/results/e6c/e6c2ac69682f409f9ee78a3a6155ae356c3368a4/
> http://autobuild.buildroot.net/results/558/558ccb0e475bfb434685c580d86f6c634238a084/
> http://autobuild.buildroot.net/results/249/24901b2dfc92b516f74054ea7bb71e1ccfc3f12f/
> 
> and many more.
> 
> Cc: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> v2:
>    Fix is now upstream
>    Adopt upstream change s/WITH_EVENTFD_GLIBC_EXT/WITH_EVENTFD_READ_WRITE/
> ---
>  package/freerdp/0001-add-support-for-uclibc.patch | 48 +++++++++++++++++++----
>  1 file changed, 41 insertions(+), 7 deletions(-)

Applied, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2015-05-01  8:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-01  3:36 [Buildroot] [PATCH v2] freerdp: fix build with uclibc snapshot and uclibc-ng Baruch Siach
2015-05-01  8:17 ` 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=20150501101730.457d4126@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