From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] libsigrok: bump version to 0.5.1
Date: Mon, 31 Dec 2018 15:59:03 +0100 [thread overview]
Message-ID: <20181231155903.07e4ae51@windsurf> (raw)
In-Reply-To: <20181230101641.GD14286@scaer>
Hello,
On Sun, 30 Dec 2018 11:16:41 +0100, Yann E. MORIN wrote:
> You forgot to propagate this new dependency to at least sigrock-cli,
> which selects libsigrok:
>
> WARNING: unmet direct dependencies detected for BR2_PACKAGE_LIBSIGROK
> Depends on [n]: BR2_USE_WCHAR [=y] && BR2_TOOLCHAIN_HAS_THREADS [=y] && BR2_USE_MMU [=y] && BR2_ENABLE_LOCALE [=n] && !BR2_STATIC_LIBS [=n] && BR2_TOOLCHAIN_GCC_AT_LEAST_4_7 [=y]
> Selected by [y]:
> - BR2_PACKAGE_SIGROK_CLI [=y] && BR2_USE_WCHAR [=y] && BR2_TOOLCHAIN_HAS_THREADS [=y] && BR2_USE_MMU [=y] && !BR2_STATIC_LIBS [=n] && BR2_TOOLCHAIN_GCC_AT_LEAST_4_7 [=y]
Thanks for the report, I fixed that in sigrok-cli and pulseview. I
guess we don't have a toolchain that has all these features, but not
locale support in our autobuilders.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-12-31 14:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-17 14:12 [Buildroot] [PATCH 1/3] libsigrok: bump version to 0.5.1 Bartosz Golaszewski
2018-11-17 14:12 ` [Buildroot] [PATCH 2/3] libsigrokdecode: bump version to 0.5.2 Bartosz Golaszewski
2018-11-17 21:00 ` Peter Korsgaard
2018-11-17 14:12 ` [Buildroot] [PATCH 3/3] pulseview: bump version to 0.4.1 Bartosz Golaszewski
2018-11-17 21:00 ` Peter Korsgaard
2018-11-17 21:00 ` [Buildroot] [PATCH 1/3] libsigrok: bump version to 0.5.1 Peter Korsgaard
2018-12-30 10:16 ` Yann E. MORIN
2018-12-31 14:59 ` Thomas Petazzoni [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=20181231155903.07e4ae51@windsurf \
--to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox