From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH] package/util-linux: build libraries as a separate package
Date: Tue, 7 May 2019 21:54:24 +0200 [thread overview]
Message-ID: <20190507215424.791e69d3@windsurf> (raw)
In-Reply-To: <20190507165158.10427-1-unixmania@gmail.com>
Hello Carlos,
On Tue, 7 May 2019 13:51:58 -0300
unixmania at gmail.com wrote:
> The findmount and lsblk utilities need udev to work correctly but cannot
> be built with udev support because the packages providing libudev (eudev
> and systemd) depend on util-linux, creating a chicken-egg problem. Solve
> it by means of the following changes:
Thanks a lot for working on this topic. It is obviously becoming a
nightmare :-/
> - Add the util-linux-libs package, which provides libblkid, libfdisk,
> libmount, libsmartcols and libuuid. It needs a small patch to
> install the uuidd.h header, used to build the uuidd utility.
> - Make util-linux depend on util-linux-libs and build only the programs.
> This requires a quite intrusive patch that modifies Makefile.am and
> some Makemodule.am files, thus requiring AUTORECONF.
Could you get in touch with upstream util-linux, expose the problem,
and see if they would be willing to merge some changes that would help
building only the programs ?
The best would of course be for upstream to realize that there is now a
circular dependency, and that it should be broken up by splitting
util-linux upstream itself in two separate projects.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-05-07 19:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 16:51 [Buildroot] [RFC PATCH] package/util-linux: build libraries as a separate package unixmania at gmail.com
2019-05-07 19:54 ` Thomas Petazzoni [this message]
2019-05-07 20:40 ` Yann E. MORIN
2019-05-07 22:12 ` Carlos A. M. dos Santos
2019-05-07 23:27 ` Arnout Vandecappelle
2019-05-09 14:34 ` Carlos A. M. dos Santos
2019-05-07 22:13 ` Carlos A. M. dos Santos
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=20190507215424.791e69d3@windsurf \
--to=thomas.petazzoni@bootlin.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 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.