From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9436] New: e2fsprogs remove busybox applets even of unselected e2fsprogs components
Date: Sat, 19 Nov 2016 18:27:54 +0000 [thread overview]
Message-ID: <bug-9436-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=9436
Bug ID: 9436
Summary: e2fsprogs remove busybox applets even of unselected
e2fsprogs components
Product: buildroot
Version: 2016.08
Hardware: All
OS: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: Jorgen.Pihlflyckt at ajeco.fi
CC: buildroot at uclibc.org
Target Milestone: ---
Hello.
Recently, I built an embedded rootfs with the extended attributes of ext2/3/4
filesystem in use, so I needed the "chattr" and "lsattr" utilities. Since they
are present in busybox, I selected them using "make busybox-menuconfig".
However, I also needed a more full-fledged mkfs from e2fsprogs, so I chose the
BR2_PACKAGE_E2FSPROGS option using the normal menuconfig procedure. This
apparently overrides (and also removes) the corresponding busybox applets. Even
the unselected ones.
What happens is this:
- When busybox is built, it's installed into the target directory, along with
the selected chattr and lsattr applet symlinks.
- At a later stage, e2fsprogs is built and installed into the target
directory. The busybox versions of the e2fsprogs utilities (the symlinks) are
removed, also the unselected ones, thus removing the previously built chattr
and lsattr busybox applets.
----
Jorgen.Pihlflyckt at ajeco.fi
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-11-19 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-19 18:27 bugzilla at busybox.net [this message]
2016-11-25 20:59 ` [Buildroot] [Bug 9436] e2fsprogs remove busybox applets even of unselected e2fsprogs components bugzilla at busybox.net
2017-04-02 3:04 ` bugzilla at busybox.net
2017-04-10 3:44 ` bugzilla at busybox.net
2017-04-11 23:05 ` bugzilla at busybox.net
2017-04-11 23:06 ` bugzilla at busybox.net
2017-05-07 14:08 ` bugzilla at busybox.net
2017-05-08 7:12 ` 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-9436-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox