From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10281] New: lsblk does not compile for util-linux
Date: Wed, 30 Aug 2017 20:06:29 +0000 [thread overview]
Message-ID: <bug-10281-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=10281
Bug ID: 10281
Summary: lsblk does not compile for util-linux
Product: buildroot
Version: 2017.05.1
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: adyke at harris.com
CC: buildroot at uclibc.org
Target Milestone: ---
lsblk is not compiled with util-linux
Commit 031659024b3cf27bb68dc58d07519b563ef472a1 indicates the
BR2_PACKAGE_UTIL_LINUX_LSBLK option was removed when upgrading to util-linux
2.28.2 since that version always built lsblk.
However, in when using buildroot 2017.05.2 (which uses util-linux 2.29.2) lsblk
is not built.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-08-30 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 20:06 bugzilla at busybox.net [this message]
2017-08-31 13:31 ` [Buildroot] [Bug 10281] lsblk does not compile for util-linux bugzilla at busybox.net
2017-08-31 13:38 ` bugzilla at busybox.net
2017-10-13 13:38 ` 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-10281-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.