Bruce Dubbs wrote:
> I used the following instructions:
> 
> liblzma_CFLAGS="-I/usr/include" \
> liblzma_LIBS="-L/lib -llzma"    \
> zlib_CFLAGS="-I/usr/include"    \
> zlib_LIBS="-L/lib -lz"          \
> ./configure --prefix=/usr     --bindir=/sbin --libdir=/lib \
>              --sysconfdir=/etc --with-xz      --with-zlib
> 
> # Note bindir

Hmm.

I suppose this only matters if someone starts providing scripts that do
something like "/bin/kmod install foo", but I had *assumed* (perhaps
naively) that "kmod in /bin" was the new API.

Not that much of anything calls kmod, although I can see future versions
of the nvidia X driver doing it to autoload their kernel module.  (I'm
pretty sure they fork and exec /sbin/modprobe today.)

> The only file here that looks out of place is libkmod.la, which probably 
> needs to be in /usr/lib.

Sigh, libtool.  :-)

There's no way to override that one in the Makefile (except resetting
libdir, but that will also put the shared libs in the wrong place).

It may be possible to move it after installation.  On the other hand,
programs that use libtool to find it will just point libtool at
/lib/libkmod.la, and everything will work; i.e. it's exactly the same as
libkmod.so (which is also left in /lib by the instructions).

So I think it'd be OK to leave it there.  Sure, it doesn't exactly match
the /usr versus / split, but it's tiny, and libtool will definitely work
with it there.

Attachment: signature.asc
Description: OpenPGP digital signature

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to