From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux v2.24-rc2
Date: Fri, 11 Oct 2013 22:34:49 -0500 [thread overview]
Message-ID: <5258C359.9010407@gmail.com> (raw)
In-Reply-To: <20131011114403.GB24613@x2.net.home>
Karel Zak wrote:
>
> The util-linux release v2.24-rc2 is available at
>
> ftp://ftp.kernel.org/pub/linux/utils/util-linux/v2.24/
>
> Feedback and bug reports, as always, are welcomed.
When I run:
./configure --disable-su --disable-sulogin --disable-login
I get:
util-linux 2.24-rc2
prefix: /usr
exec prefix: ${prefix}
localstatedir: /run
bindir: /lib
sbindir: ${exec_prefix}/sbin
libdir: ${exec_prefix}/lib
includedir: ${prefix}/include
usrbin_execdir: ${exec_prefix}/bin
usrsbin_execdir: ${exec_prefix}/sbin
usrlib_execdir: ${exec_prefix}/lib
compiler: gcc -std=gnu99
cflags: -g -O2
suid cflags:
ldflags:
suid ldflags:
Python:
Python version:
Python libs:
Surely bindir should not be /lib. I can't even override it with
--bindir=/bin
Indeed, if I make && make DESTDIR=/tmp/util-linux install I get:
$ ls /tmp/util-linux/lib
dmesg findmnt kill lsblk more mount mountpoint umount wdctl
I'm not an autotools expert, but I tried changing line 55 in
configure.ac to
AS_CASE([$libdir], ['${exec_prefix}/lib'], [libdir=/lib; ...
^^^
and not
AS_CASE([$libdir], ['${exec_prefix}/lib'], [bindir=/lib;
But that's not right either because it changes bindir to /sbin and not /bin.
Also, a lot of executables are placed in /usr/sbin when the default
should be /sbin. Examples are swapon, fsck*, mkfs*, etc.
-- Bruce
next prev parent reply other threads:[~2013-10-12 3:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 11:44 [ANNOUNCE] util-linux v2.24-rc2 Karel Zak
2013-10-11 11:44 ` Karel Zak
2013-10-12 3:34 ` Bruce Dubbs [this message]
2013-10-14 7:52 ` Karel Zak
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=5258C359.9010407@gmail.com \
--to=bruce.dubbs@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 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.