From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Tanu Kaskinen <tanu.kaskinen@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] speex, speexdsp: 1.2rc1 -> 1.2rc2/1.2rc3
Date: Sat, 11 Jul 2015 23:42:02 +0100 [thread overview]
Message-ID: <1436654522.3310.30.camel@linuxfoundation.org> (raw)
In-Reply-To: <1436438943.23019.26.camel@tkkaskin-mobl3.ger.corp.intel.com>
On Thu, 2015-07-09 at 13:49 +0300, Tanu Kaskinen wrote:
> I sent now v2 of the patches, which should fix the alsa-plugins build
> failures.
Thanks, those do indeed seem resolved.
> The libspeexdsp-dev problem is more difficult, and I don't really know
> how to debug it further. The error message was:
>
> error: Can't install pulseaudio-dev-6.0-r0@core2_32: no package provides libspeexdsp-dev
>
> However, "bitbake speexdsp" seems to generate the libspeexdsp-dev
> package just fine (libspeexdsp-dev_1.2rc3-r0_core2-64.ipk appears in the
> deploy directory).
Oddly enough, it happened again with the new patches:
https://autobuilder.yoctoproject.org/main/builders/nightly-x86-lsb/builds/389/steps/BuildImages_1/logs/stdio
It only seems to happen on x86-lsb, not any other architecture. Why? No
idea as yet :/.
Cheers,
Richard
next prev parent reply other threads:[~2015-07-11 22:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 15:14 [PATCH 0/3] speex, speexdsp: 1.2rc1 -> 1.2rc2/1.2rc3 Tanu Kaskinen
2015-07-06 15:14 ` [PATCH 1/3] speexdsp: initial recipe Tanu Kaskinen
2015-07-06 15:14 ` [PATCH 2/3] speex: 1.2rc1 -> 1.2rc2 Tanu Kaskinen
2015-07-06 15:14 ` [PATCH 3/3] alsa-plugins, pulseaudio: depend on speexdsp, not speex Tanu Kaskinen
2015-07-07 13:23 ` [PATCH 0/3] speex, speexdsp: 1.2rc1 -> 1.2rc2/1.2rc3 Alexander Kanavin
2015-07-09 7:58 ` Richard Purdie
2015-07-09 8:11 ` Tanu Kaskinen
2015-07-09 10:49 ` Tanu Kaskinen
2015-07-11 22:42 ` Richard Purdie [this message]
2015-07-15 7:40 ` Richard Purdie
2015-07-15 8:25 ` Andre McCurdy
2015-07-22 7:02 ` Richard Purdie
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=1436654522.3310.30.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=tanu.kaskinen@linux.intel.com \
/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.