From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15665] consider adding xfstests-dev
Date: Tue, 27 Jun 2023 12:02:41 +0000 [thread overview]
Message-ID: <bug-15665-163-RKL48xA0h8@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15665-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15665
--- Comment #3 from Andreas Ziegler <br015@umbiko.net> ---
Activate System tools -> util-linux -> basic set:
config BR2_PACKAGE_UTIL_LINUX_BINARIES
bool "basic set"
...
help
Install the basic set of util-linux binaries.
blkdiscard, blkid, blockdev, chcpu, choom, col, colcrt, colrm,
column, ctrlaltdel, dmesg, fdisk, fincore, findfs, findmnt,
flock, fsfreeze, fstrim, getopt, hexdump, ipcmk, isosize,
ldattach, look, lsblk, lscpu, lsipc, lslocks, lsns, mcookie,
mkfs, mkswap, namei, prlimit, readprofile, renice, rev,
rtcwake, script, scriptlive, scriptreplay, setarch, setsid,
sfdisk, swaplabel, swapoff, swapon, uuidgen, uuidparse,
whereis, wipefs
...
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-06-27 12:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-25 7:11 [Buildroot] [Bug 15665] New: consider adding xfstests-dev bugzilla
2023-06-25 7:59 ` [Buildroot] [Bug 15665] " bugzilla
2023-06-27 7:52 ` bugzilla
2023-06-27 12:02 ` bugzilla [this message]
2023-06-27 15:04 ` bugzilla
2023-06-27 15:27 ` bugzilla
2023-06-27 17:49 ` bugzilla
2023-06-27 17:53 ` bugzilla
2023-06-27 20:02 ` bugzilla
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-15665-163-RKL48xA0h8@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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