From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] broken alsa-lib
Date: Mon, 23 Feb 2009 09:44:24 +0100 [thread overview]
Message-ID: <877i3h4k5z.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090222232955.GA10011@buzzloop.caiaq.de> (Daniel Mack's message of "Mon\, 23 Feb 2009 00\:29\:55 +0100")
>>>>> "Daniel" == Daniel Mack <daniel@caiaq.de> writes:
Hi,
>> Alsa-lib had an issue with !LARGEFILE support that we fixed recently
>> and pushed upstream, but other than that I don't remember any
>> bugreports.
Daniel> Hmm, what I see is certainly not a LARGEFILE issue.
Probably not, just mentioning the only bugs we've found in alsa lib
recently.
>> You mentioned something about 1.0.19, but buildroot is still using
>> 1.0.18, are you using some local changes?
Daniel> Yes, true, forgot to mention that. We locally patched to use
Daniel> 1.0.19 but that was merely because I hoped to fix the problem
Daniel> by that - the same problem exists with 1.0.18. And I got this
Daniel> problem since a long time and always patched my way around it
Daniel> (by overriding the value with some hard-coded constant) as I
Daniel> thought it is a minor issue that will be fixed sooner or
Daniel> later. But as it turns out, the problem seems to be bigger
Daniel> and might also have other impact than just that single
Daniel> failing function call.
Please report those kind of problems to us so we have a chance to fix
them. This is the first I hear of it.
Daniel> I'll build alsa-lib and alsa-utils with OE tomorrow and see
Daniel> whether that makes any difference.
Great, Please send us the config.log from OE and BR if it works under
OE.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-02-23 8:44 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 [this message]
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
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=877i3h4k5z.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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