util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Carlos A. M. dos Santos" <unixmania@gmail.com>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: Building util-linux libraries and utilities as separated operations
Date: Tue, 7 May 2019 09:55:42 -0300	[thread overview]
Message-ID: <CAJ4jsacmP4e4EpnXSPL_C0Zd7GuwJvyrTqmPeirukDAYW7L5ow@mail.gmail.com> (raw)
In-Reply-To: <20190507103055.lqamhi3qbbp4er7l@ws.net.home>

On Tue, May 7, 2019 at 7:31 AM Karel Zak <kzak@redhat.com> wrote:
>
> On Mon, May 06, 2019 at 10:22:51AM -0300, Carlos A. M. dos Santos wrote:
> > Would it be possible to build/install the libraries first and the
> > utilities later, using the previously installed libraries? That would
> > help to solve a chicken-egg problem between lsblk, and libudev, as
> > described in
> >
> >     https://bugs.busybox.net/show_bug.cgi?id=11811
>
>  It always uses in-tree libs to compile in-tree utilities.
>
>  Anyway, all external dependencies are optional. For example you can
>  compile lsblk without udev. It's also possible to specify wanted stuff,
>  for example:
>
>      ./configure --disable-all-programs --enable-libmount \
>                  --enable-libblkid --enable-libuuid
>
>  to compile only libs.
>
>  The best way is probably do it in two steps, in the first step
>  without dependencies, and in the second step rebuild all with
>  dependencies. For example:
>
>  stage 1:
>     ./configure  --without-ncurses --without-tinfo \
>                  --without-python --without-systemd \
>                  --without-udev
>
>     make install
>
>     ... compile udev, install libudev ...
>
>  stage 2:
>     ./configure
>     make install

This works but the libraries are build and installed twice, which is
undesirable. Is there a way to skip the library installation in the
second step?

>
>  If I good remember distro bootstrap with util-linux is nothing unique
>  and it's used by Fedora, Suse, linuxfromscratch.org, ...
>
>
>  IMHO distro bootstrap is very special situation. For regular updates
>  is probably better to build util-linux in build root where are
>  already installed all dependencies (e.g. libudev) from previous
>  versions.
>
>     Karel
>
> --
>  Karel Zak  <kzak@redhat.com>
>  http://karelzak.blogspot.com

-- 
Carlos Santos <unixmania@gmail.com>

      reply	other threads:[~2019-05-07 12:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-06 13:22 Building util-linux libraries and utilities as separated operations Carlos A. M. dos Santos
2019-05-07 10:30 ` Karel Zak
2019-05-07 12:55   ` Carlos A. M. dos Santos [this message]

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=CAJ4jsacmP4e4EpnXSPL_C0Zd7GuwJvyrTqmPeirukDAYW7L5ow@mail.gmail.com \
    --to=unixmania@gmail.com \
    --cc=kzak@redhat.com \
    --cc=util-linux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).