linux-kernel - Re: [ANNOUNCE] util-linux-ng v2.16-rc2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 2 Jul 2009 22:32:01 +0200
From:	Kay Sievers <kay.sievers@...y.org>
To:	Karel Zak <kzak@...hat.com>
Cc:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	util-linux-ng@...r.kernel.org
Subject: Re: [ANNOUNCE] util-linux-ng v2.16-rc2

On Thu, Jul 2, 2009 at 20:10, Karel Zak<kzak@...hat.com> wrote:
>
> The second util-linux-ng 2.16 release candidate is available at
>
>   ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/v2.16/
>
> Feedback and bug reports, as always, are welcomed.

It builds fine on the host, but fails to build in a clean chroot:

The hack with moving the devel files around to /usr with an install
hook breaks the values stored in the libblkid.la file and relinking
fails, because the lib devel files are now no longer in /lib but
(silently) moved to /usr/lib:

libtool: relink: gcc -std=gnu99 -shared  .libs/cache.o .libs/dev.o
.libs/devname.o .libs/devno.o .libs/getsize.o .libs/llseek.o
.libs/probe.o .libs/read.o .libs/resolve.o .libs/save.o .libs/tag.o
.libs/version.o .libs/verify.o .libs/encode.o .libs/config.o
.libs/evaluate.o .libs/blkdev.o .libs/linux_version.o
.libs/canonicalize.o .libs/md5.o  -Wl,--whole-archive
probers/.libs/libblkid_probers.a -Wl,--no-whole-archive
-L/var/tmp/util-linux-2.16-build/lib64 -L/lib64 -luuid
-Wl,--version-script=../../../shlibs/blkid/src/blkid.sym   -Wl,-soname
-Wl,libblkid.so.1 -o .libs/libblkid.so.1.0.0
/usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../x86_64-suse-linux/bin/ld:
cannot find -luuid
collect2: ld returned 1 exit status

That the .so is installed in the root is really the implementation
detail that should be hidden from anything but the ld loader on the
system. I guess, we want to keep the original --libdir value, and use
a --rootlibdir as it's own parameter, or something similar, and just
move the .so image to the root with the install hook (or the spec
file), instead of moving the devel stuff, faking the .pc files and
patching the .la files. :)

Thanks,
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/