Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/kodi: not available using a musl-based toolchain
Date: Sun, 24 Apr 2016 13:14:31 +0200	[thread overview]
Message-ID: <ndmuucxj3a.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20160127213046.34c7cee3@free-electrons.com

Am Wed, 27 Jan 2016 21:30:46 +0100 schrieb Thomas Petazzoni:

>> > And what happens if you add an additional case to support musl ?
>> 
>> Hi Thomas,
>> 
>> the build will fail:
[...]
>> 
>> I know these problems are fixable and the voidlinux projects seems to
>> have done it already for 15.2-Isengard:
>> https://github.com/voidlinux/void-
>> packages/tree/99f74705bc6520297d689fae4bcc9606c71ad34f/srcpkgs/kodi/
>> patches
>> 
[...]
> 
> Thanks for the explanation. Ideally, this should have been part of the
> commit log from the beginning, so that we keep in the git history the
> real reason for disabling Kodi on musl.

Hi Thomas,

with my latest PR I started the process to add musl support to Kodi:
https://github.com/xbmc/xbmc/pull/9672

I am curious for the reaction from upstream ;)

Regards, Bernd

      reply	other threads:[~2016-04-24 11:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26 22:44 [Buildroot] [PATCH 1/2] package/kodi: not available using a musl-based toolchain Bernd Kuhls
2016-01-26 22:44 ` [Buildroot] [PATCH 2/2] package/kodi: reorder select/depends Bernd Kuhls
2016-01-27  8:22 ` [Buildroot] [PATCH 1/2] package/kodi: not available using a musl-based toolchain Thomas Petazzoni
2016-01-27 20:17   ` Bernd Kuhls
2016-01-27 20:30     ` Thomas Petazzoni
2016-04-24 11:14       ` Bernd Kuhls [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=ndmuucxj3a.ln2@ID-313208.user.individual.net \
    --to=bernd.kuhls@t-online.de \
    --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