public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/lvm2: add missing dependency to lvmetad
Date: Mon, 20 Apr 2020 17:25:57 +0200	[thread overview]
Message-ID: <20200420152557.824148-1-fontaine.fabrice@gmail.com> (raw)

Commit 9889b8ce7fcef50fb5089f6e3e84b54f730d0ca6 forgot to propagate
dependency from lvm2-app-library to lvmetad

Fixes:
 - No autobuilder failures yet

Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
---
 package/lvm2/Config.in | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/package/lvm2/Config.in b/package/lvm2/Config.in
index a41bb053b5..a9c5c453fc 100644
--- a/package/lvm2/Config.in
+++ b/package/lvm2/Config.in
@@ -49,6 +49,7 @@ comment "lvm2 application library needs a glibc or uClibc toolchain"
 
 config BR2_PACKAGE_LVM2_LVMETAD
 	bool "install lvmetad"
+	depends on !BR2_TOOLCHAIN_USES_MUSL # lvm2-app-library
 	select BR2_PACKAGE_LVM2_APP_LIBRARY
 	help
 	  Install lvmetad
@@ -60,6 +61,9 @@ config BR2_PACKAGE_LVM2_LVMETAD
 	  system.  lvmetad can be a disadvantage when disk event
 	  notifications from the system are unreliable.
 
+comment "lvmetad daemon needs a glibc or uClibc toolchain"
+	depends on BR2_TOOLCHAIN_USES_MUSL
+
 endif
 
 comment "lvm2 needs a toolchain w/ threads, dynamic library"
-- 
2.25.1

             reply	other threads:[~2020-04-20 15:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20 15:25 Fabrice Fontaine [this message]
2020-04-20 15:59 ` [Buildroot] [PATCH 1/1] package/lvm2: add missing dependency to lvmetad 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=20200420152557.824148-1-fontaine.fabrice@gmail.com \
    --to=fontaine.fabrice@gmail.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