All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: jon@jonshouse.co.uk
Cc: alsa-devel@alsa-project.org
Subject: Re: Random process lockup on ARM board: alsa-lib-1.0.25, FUTEX_WAIT_PRIVATE
Date: Thu, 08 Mar 2012 09:53:03 +0100	[thread overview]
Message-ID: <4F58736F.6010500@ladisch.de> (raw)
In-Reply-To: <1329933773.24266.44.camel@jonspc>

Jonathan Andrews wrote:
> On Wed, 2012-02-22 at 17:23 +0100, Clemens Ladisch wrote:
>> Now it doesn't use any pthread functions.
>
> Thanks, use or require ? Still complains if I static compile my
> application but don't link with pthreads.

Please try with the patch below; this should remove the last
occurence of pthreads in alsa-lib.


Regards,
Clemens


--- alsa-lib/configure.in
+++ alsa-lib/configure.in
@@ -512,6 +512,7 @@ if test "$HAVE_LIBDL" != "yes"; then
 fi

 if test "$HAVE_LIBPTHREAD" != "yes"; then
+  build_pcm_meter="no"
   build_pcm_share="no"
 fi

  parent reply	other threads:[~2012-03-08  8:49 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-16 12:01 Random process lockup on ARM board: alsa-lib-1.0.25, FUTEX_WAIT_PRIVATE Jonathan Andrews
2012-02-17 21:04 ` Jonathan Andrews
2012-02-18 13:02   ` Jonathan Andrews
2012-02-18 20:36     ` Clemens Ladisch
     [not found]       ` <1329603022.1089.57.camel@jonspc>
2012-02-20  7:54         ` Clemens Ladisch
     [not found]           ` <1329926198.22918.10.camel@jonspc>
2012-02-22 16:23             ` Clemens Ladisch
2012-02-24  0:29               ` Jonathan Andrews
2012-02-29  9:12                 ` Huang Shijie
2012-03-07 20:07                   ` Darren Hart
2012-03-07 21:22                     ` Jonathan Andrews
2012-03-08  3:42                       ` Darren Hart
2012-03-08  2:28                     ` Huang Shijie
2012-03-08  3:36                       ` Darren Hart
2012-03-08  4:24                         ` Huang Shijie
2012-03-08  7:40                           ` Darren Hart
2012-03-08  8:43                             ` Huang Shijie
     [not found]               ` <1329933773.24266.44.camel@jonspc>
2012-03-08  8:53                 ` Clemens Ladisch [this message]
     [not found]                   ` <1331199625.22455.7.camel@jonspc>
     [not found]                     ` <4F588213.2030600@ladisch.de>
     [not found]                       ` <1331203724.22455.44.camel@jonspc>
2012-03-08 11:43                         ` Clemens Ladisch
2012-03-08 13:04                           ` Jonathan Andrews
2012-03-08 13:47                           ` Jonathan Andrews
2012-03-08 14:35                             ` Clemens Ladisch
2012-03-08 15:14                               ` Jonathan Andrews
2012-03-08 15:34                                 ` Takashi Iwai
2012-03-08 16:42                                   ` Jonathan Andrews
2012-03-08 19:05                                   ` Jonathan Andrews
2012-03-08 20:40                                     ` Clemens Ladisch
2012-03-08 21:42                                       ` Jonathan Andrews
2012-03-14 13:18                                       ` Jonathan Andrews

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=4F58736F.6010500@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=jon@jonshouse.co.uk \
    /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.