Ken Moffat wrote:
>
> Obviously /lib64 because you are on multilib. We'll use /lib, but
> I guess the shared lib needs to be accessible from /usr/lib.
We really don't want udev libraries on /usr. They are used early in the
boot process before (potentially) mounting /usr.
Perhaps it's because I invested so much work in the last couple of days,
but I am leaning towards static linking of udevd and udevadm. At least
the udev part.
# ldd /sbin/udevadm
linux-vdso.so.1 (0x00007fff50bff000)
libblkid.so.1 => /lib/libblkid.so.1 (0x00007f33d72dc000)
libkmod.so.2 => /lib64/libkmod.so.2 (0x00007f33d70c8000)
librt.so.1 => /lib/librt.so.1 (0x00007f33d7502000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00007f33d686e000)
libc.so.6 => /lib/libc.so.6 (0x00007f33d64ca000)
libuuid.so.1 => /lib/libuuid.so.1 (0x00007f33d6cad000)
liblzma.so.5 => /lib64/liblzma.so.5 (0x00007f33d6a8b000)
libz.so.1 => /lib/libz.so.1 (0x00007f33d6eb1000)
libdl.so.2 => /lib/libdl.so.2 (0x00007f33d770a000)
/lib64/ld-linux-x86-64.so.2 (0x00007f33d790e000)
When I look at udev-182, it appears that the programs are statically
linked too. The only difference is that -182 doesn't have libdl.so.2.
That's a mistake in my script since it links fine without it.
Investigating some more, the none of the udev programs need libz, libdl,
liblzma, or libuuid however,
libuuid.so.1 needed by libblkid.so
liblzma.so.5 needed by libkmod.so
libz.so.1 needed by libkmod.so
These don't need to be specified in the link line, but are pulled in
automatically.
What this all means is that there is no need to install any udev
libraries or .h files or supporting .pc, .la, .lo etc files.
-- Bruce
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
