From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/espeak: add comment to ignore 'unmet dependencies'
Date: Mon, 8 May 2017 21:49:11 +0200 [thread overview]
Message-ID: <20170508214911.6c0abdb4@free-electrons.com> (raw)
In-Reply-To: <20170507203856.5328-1-yann.morin.1998@free.fr>
Hello,
On Sun, 7 May 2017 22:38:56 +0200, Yann E. MORIN wrote:
> On master 86b4eeccc4, espeak can generate spurious 'unmet dependencies'
> messages:
>
> $ make KCONFIG_SEED=0x7A85DEE0 randconfig
> warning: (BR2_PACKAGE_ESPEAK_AUDIO_BACKEND_ALSA) selects
> BR2_PACKAGE_PORTAUDIO_CXX which has unmet directdependencies
> (BR2_PACKAGE_PORTAUDIO && BR2_INSTALL_LIBSTDCPP)
>
> However, the dpendency chain *is* correct. There is something that
> causes the kconfig parser to get really confused...
>
> Add a comment statng the issue is spurious, so noone tries to fix it.
Indeed, I don't see anything wrong in this dependency chain.
> config BR2_PACKAGE_ESPEAK_AUDIO_BACKEND_ALSA
> bool "alsa via portaudio"
> + # Selecting portaudio generates spurious "unmet dependencies"
> + # warnings. Unless you are changing the dependencies of espeak
> + # or portaudio, just ignore those spurious warnings.
> select BR2_PACKAGE_PORTAUDIO
> select BR2_PACKAGE_PORTAUDIO_CXX
Perhaps we could simply add a "depends on BR2_INSTALL_LIBSTDCPP" here,
which most likely would silence the warning?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-08 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-07 20:38 [Buildroot] [PATCH] package/espeak: add comment to ignore 'unmet dependencies' Yann E. MORIN
2017-05-08 19:49 ` Thomas Petazzoni [this message]
2017-05-08 20:46 ` Yann E. MORIN
2017-05-11 19:54 ` Thomas Petazzoni
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=20170508214911.6c0abdb4@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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 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.