From: Daniel Mack <daniel@caiaq.de>
To: buildroot@busybox.net
Subject: [Buildroot] broken alsa-lib
Date: Mon, 23 Feb 2009 10:42:26 +0100 [thread overview]
Message-ID: <20090223094226.GA15722@buzzloop.caiaq.de> (raw)
In-Reply-To: <49A268F5.5030300@carallon.com>
On Mon, Feb 23, 2009 at 09:14:29AM +0000, Will Wagner wrote:
>> as pointed out in two threads on the alsa-dev ML, there seems to be
>> general problem with ALSA libraries built by buildroot:
>>
>> http://mailman.alsa-project.org/pipermail/alsa-devel/2009-February/014999.html
>> http://mailman.alsa-project.org/pipermail/alsa-devel/2009-February/015005.html
>>
>> Any hints, anyone?
>
> Not sure if this is the same as a problem I was seeing with alsa-lib. It
> was a while ago so not entirely sure. However I found my problem was to
> do with the complicated alsa versioning API meaning that the wrong
> version of the function was called. I fixed it by adding
> --with-versioned="no" to the alsa-lib configure (I also moved to 1.0.19
> as that had a number of bug fixes for other things I needed).
Aha, that fixed it for me, too. Thanks :)
Daniel
prev parent reply other threads:[~2009-02-23 9:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-22 22:43 [Buildroot] broken alsa-lib Daniel Mack
2009-02-22 23:16 ` Peter Korsgaard
2009-02-22 23:29 ` Daniel Mack
2009-02-23 8:44 ` Peter Korsgaard
2009-02-23 12:09 ` Daniel Mack
2009-02-23 12:28 ` Peter Korsgaard
2009-02-23 12:46 ` Daniel Mack
2009-03-01 9:43 ` Peter Korsgaard
2009-03-02 1:05 ` Daniel Mack
2009-03-02 6:27 ` Peter Korsgaard
2009-02-23 9:14 ` Will Wagner
2009-02-23 9:22 ` Peter Korsgaard
2009-02-23 9:45 ` Will Wagner
2009-02-23 11:10 ` Peter Korsgaard
2009-02-23 9:45 ` Daniel Mack
2009-02-23 11:11 ` Peter Korsgaard
2009-02-23 11:14 ` Will Wagner
2009-02-23 9:42 ` Daniel Mack [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=20090223094226.GA15722@buzzloop.caiaq.de \
--to=daniel@caiaq.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