Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC v1] directfb: fix musl compile
Date: Wed, 18 Nov 2015 22:57:10 +0100	[thread overview]
Message-ID: <87vb8z9djd.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1447110344-1446-1-git-send-email-ps.report@gmx.net> (Peter Seiderer's message of "Tue, 10 Nov 2015 00:05:44 +0100")

>>>>> "Peter" == Peter Seiderer <ps.report@gmx.net> writes:

Hi,

 > - use 'union sigval' instead of sigval_t (same as suggested
 >   for canfestival by Yann E. MORIN, see [2])

 > - delete DIRECT_RECURSIVE_MUTEX_INITIALIZER define (which uses unknown
 >   PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP)

 > - use DIRECT_MUTEX_INITIALIZER instead for trace.c (no recursive
 >   mutex needed)

 > - use pthread_once and direct_recursive_mutex_init instead for
 >   directfb.c

 > Fixes [1]:

 >   system.c:114:6: error: unknown type name 'sigval_t'

 > and

 >   ../lib/direct/os/linux/glibc/mutex.h:49:53: error: ?PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP? undeclared (first use in this function)

 > [1] http://autobuild.buildroot.net/results/548/548bf7b800a946e97135c0ba66363f388e517d6f
 > [2] https://patchwork.ozlabs.org/patch/509731

 > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
 > ---
 > RFC: not yet runtime tested

Thanks, but I don't feel confident applying such a patch, especially as
upstream seems dead so we cannot get their feedback on it / will have to
carry it along ourselves - So I've instead marked directfb as !musl.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2015-11-18 21:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09 23:05 [Buildroot] [RFC v1] directfb: fix musl compile Peter Seiderer
2015-11-18 21:57 ` Peter Korsgaard [this message]
2015-11-19 19:12   ` Peter Seiderer

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=87vb8z9djd.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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