From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11811] New: lsblk (util-linux) should depend on libudev if available
Date: Tue, 30 Apr 2019 03:02:40 +0000 [thread overview]
Message-ID: <bug-11811-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11811
Bug ID: 11811
Summary: lsblk (util-linux) should depend on libudev if
available
Product: buildroot
Version: 2019.02.2
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: pmorici at dev295.com
CC: buildroot at uclibc.org
Target Milestone: ---
Several of the output columns of lsblk such as SERIAL and WWN are incorrectly
reported as empty strings. ie: 'lsblk -do SERIAL'
The cause is that lsblk uses libudev to obtain this information but the
util-linux package doesn't list the udev package as a dependency if it is
selected. If util-linux gets built before udev then many parts of lsblk return
empty strings for various fields.
Adding the following to packages/util-linux/util-linux.mk fixes the problem.
ifeq ($(BR2_PACKAGE_UDEV),y)
UTIL_LINUX_DEPENDENCIES += udev
endif
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-04-30 3:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 3:02 bugzilla at busybox.net [this message]
2019-04-30 7:00 ` [Buildroot] [Bug 11811] lsblk (util-linux) should depend on libudev if available bugzilla at busybox.net
2019-04-30 12:34 ` bugzilla at busybox.net
2019-04-30 12:56 ` bugzilla at busybox.net
2019-05-03 12:10 ` bugzilla at busybox.net
2019-05-03 12:19 ` bugzilla at busybox.net
2019-05-05 0:15 ` bugzilla at busybox.net
2019-05-05 2:15 ` bugzilla at busybox.net
2019-05-05 2:17 ` bugzilla at busybox.net
2019-05-05 2:21 ` bugzilla at busybox.net
2019-05-07 16:57 ` bugzilla at busybox.net
2019-05-09 17:19 ` bugzilla at busybox.net
2020-05-29 21:04 ` bugzilla at busybox.net
2020-11-04 21:57 ` bugzilla at busybox.net
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=bug-11811-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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.