From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/uclibc: Add eventfd_read() and eventfd_write()
Date: Sun, 26 Oct 2014 01:51:26 +0200 [thread overview]
Message-ID: <874mur908x.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <XnsA3D1CF411C49EberndkuhlsPkbjNfxxIA@bernd-kuhls.de> (Bernd Kuhls's message of "Sat, 25 Oct 2014 20:22:26 +0200")
>>>>> "Bernd" == Bernd Kuhls <bernd.kuhls@t-online.de> writes:
> Peter Korsgaard <jacmet@uclibc.org> wrote in
> news:87wq7p57i0.fsf at dell.be.48ers.dk:
>> Is there any real reason to use uClibc with kodi?
> Hi,
> yes, I am using kodi on an uClibc-based system (www.fli4l.de) and it works
> perfectly fine.
I'm not questioning if it is possible given enough patches, but rather
if it is worth the effort. Is there any specific reason why you are
using uClibc instead of musl or glibc?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-10-25 23:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 20:43 [Buildroot] [PATCH 1/1] package/uclibc: Add eventfd_read() and eventfd_write() Bernd Kuhls
2014-10-25 0:16 ` Peter Korsgaard
2014-10-25 18:22 ` Bernd Kuhls
2014-10-25 23:51 ` Peter Korsgaard [this message]
2014-10-26 14:15 ` Bernd Kuhls
2014-12-08 22:25 ` Yann E. MORIN
2014-12-14 10:36 ` Bernd Kuhls
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=874mur908x.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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