All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] freerdp: fix build with uclibc snapshot and uclibc-ng
Date: Wed, 29 Apr 2015 07:30:08 +0300	[thread overview]
Message-ID: <20150429043008.GA2258@tarshish> (raw)
In-Reply-To: <XnsA48AE66F8143FberndkuhlsPkbjNfxxIA@bernd-kuhls.de>

Hi Bernd,

On Tue, Apr 28, 2015 at 10:39:10PM +0200, Bernd Kuhls wrote:
> Baruch Siach <baruch@tkos.co.il> wrote in
> news:6282ca49ebfb65c9399eeedcac6a3d69038d2690.1430250053.git.baruch at tkos.co.il: 
> > 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 suggested PR.
> 
> 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.
> 
> [1] In fact it is the 2nd try ;) http://patchwork.ozlabs.org/patch/402957/

Buildroot generally does not add feature patches to packages. This is 
something to discuss with upstream. Alternatively, you may add 
eventfd_{read,write} to Kodi (upstream) to be used as needed, just like 
freerdp does.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2015-04-29  4:30 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 [this message]
2015-04-29  7:29   ` Thomas Petazzoni

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=20150429043008.GA2258@tarshish \
    --to=baruch@tkos.co.il \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.