alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Andrews <jon@jonshouse.co.uk>
To: Clemens Ladisch <clemens@ladisch.de>
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 13:04:41 +0000	[thread overview]
Message-ID: <1331211881.27232.6.camel@jonspc> (raw)
In-Reply-To: <4F589B58.6090203@ladisch.de>

On Thu, 2012-03-08 at 12:43 +0100, Clemens Ladisch wrote:
> Jonathan Andrews wrote:
> > On Thu, 2012-03-08 at 10:55 +0100, Clemens Ladisch wrote:
> >> Jonathan Andrews wrote:
> >>> I'm using this script to build both static and dynamic versions of the
> >>> alsalib. Can you check the configure arguments are correct.
> >>
> >> They look correct.
> >
> > Tried to compile my application, still fails asking for pthreads.
> 
> The configure.in file contains the patch, but the generated configure
> script does not have it (although its time stamp is newer).
> Please ensure that you've run autoconf (although make should do this
> automatically).
> 
> 
> Regards,
> Clemens

aclocal.m4:16: warning: this file was generated for autoconf 2.68.
You have another version of autoconf.  It may work, but is not
guaranteed to.
If you have problems, you may need to regenerate the build system
entirely.
To do so, use the procedure documented by the package, typically
`autoreconf'.
configure.in:15: error: Autoconf version 2.62 or higher is required
aclocal.m4:6823: AM_INIT_AUTOMAKE is expanded from...
configure.in:15: the top level
autom4te: /usr/bin/m4 failed with exit status: 63


Thanks for finding that, seems its a version problem.  My machine has
version 2.61

Upgrading now.

Thanks,
Jon

  reply	other threads:[~2012-03-08 13:04 UTC|newest]

Thread overview: 18+ 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
     [not found]               ` <1329933773.24266.44.camel@jonspc>
2012-03-08  8:53                 ` Clemens Ladisch
     [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 [this message]
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=1331211881.27232.6.camel@jonspc \
    --to=jon@jonshouse.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    /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;
as well as URLs for NNTP newsgroup(s).