From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] util-linux builds and installs lots of unwanted binaries
Date: Mon, 16 Apr 2012 17:17:52 +0200 [thread overview]
Message-ID: <1334589472.13607.15.camel@sven> (raw)
Hi,
recently udev started to depend on util-linux for libblkid. Since then
there are lots of binaries built and installs that did not asked for.
Here's an incomplete list of such binaries:
blockdev, fdformat, fsck.minix, isosize, mkfs, mkfs.bfs, mkfs.minix,
mkswap, swaplabel, sfdisk, getopt, getopt-parse.bash, getopt-parse.tcsh,
cal logger look mcookie namei whereis
Now I am wondering about the best way to change this so that only the
libraries are built and installed unless util-linux is configured
otherwise. I am looking for a solution that can be accepted in buildbot.
And if changes to util-linux are needed, then those should have a chance
to be accepted upstream in util-linux. What would you advice?
Regards,
Sven
next reply other threads:[~2012-04-16 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 15:17 Sven Neumann [this message]
2012-04-16 16:00 ` [Buildroot] util-linux builds and installs lots of unwanted binaries Gustavo Zacarias
2012-04-17 8:35 ` Sven Neumann
2012-04-17 11:08 ` Gustavo Zacarias
2012-04-17 17:08 ` Sven Neumann
2012-04-25 14:21 ` Gustavo Zacarias
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=1334589472.13607.15.camel@sven \
--to=s.neumann@raumfeld.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