All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: "Jörg Krause" <joerg.krause@embedded.rocks>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/bluez-alsa: needs alsa-lib mixer
Date: Thu, 28 Jul 2022 22:57:57 +0200	[thread overview]
Message-ID: <20220728225757.1a380e4f@windsurf> (raw)
In-Reply-To: <20220728154542.3061123-1-fontaine.fabrice@gmail.com>

On Thu, 28 Jul 2022 17:45:42 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> aplay needs alsa-lib mixer since bump to version 4.0.0 in commit
> e843433e186c6802ae0c31cb501b2212972ed725 and
> https://github.com/Arkq/bluez-alsa/commit/7050c9a81895500fe2d59ec6e4859633d4353e36:
> 
> In file included from alsa-mixer.c:11:
> alsa-mixer.h:16:21: error: unknown type name 'snd_mixer_t'; did you mean
> 'snd_timer_t'?
>    16 | int alsa_mixer_open(snd_mixer_t **mixer, snd_mixer_elem_t
>       **elem,
>       |                     ^~~~~~~~~~~
>       |                     snd_timer_t
> 
> So select BR2_PACKAGE_ALSA_LIB_MIXER instead of building aplay
> conditionally to keep backward compatibility
> 
> Fixes:
>  - http://autobuild.buildroot.org/results/d3faac6e49fe9cc21091a5dfa44780b8c63189be
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  package/bluez-alsa/Config.in | 1 +
>  1 file changed, 1 insertion(+)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-07-28 20:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28 15:45 [Buildroot] [PATCH 1/1] package/bluez-alsa: needs alsa-lib mixer Fabrice Fontaine
2022-07-28 20:57 ` Thomas Petazzoni via buildroot [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=20220728225757.1a380e4f@windsurf \
    --to=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=joerg.krause@embedded.rocks \
    --cc=thomas.petazzoni@bootlin.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.