On Sat, Feb 04, 2012 at 04:31:09PM -0600, Bruce Dubbs wrote: > Forwarding to lfs-dev. > > John Burrell wrote: > > Bruce - strictly lfs - sorry, but I'm not registered in lfs-support. > > > > I replaced module-init-tools with kmod. > > > > In the configure --libdir=/lib > > > > This means that kmod puts libkmod.pc in /lib/pkgconfig > > Yes it does. > > > Of course, there are many ways to get the pc file into > > /usr/lib/pkgconfig, where it belongs. > > > > I did: > > > > sed -i 's|pkgconfigdir = $(libdir)/pkgconfig|pkgconfigdir = > > /usr/lib/pkgconfig|' \ > Makefile.am > > > > autoreconf > > > > then as per the book. > > I took a look at my development system and I also have > /lib/pkgconfig/libtirpc.pc. > > Should we just create /usr/lib/pkgconfig as a part of Section 6.5 and > then a symlink from /lib/pkgconfig -> ../usr/lib/pkgconfig in Section 6.6? > > -- Bruce > The symlink shouldn't be needed on BLFS! For libtirpc I use:
./configure --prefix=/usr # (plus my usual --enable-static=no) make make libdir=/lib pkgconfigdir=/usr/lib/pkgconfig install ln -sfv /lib/libtirpc.so /usr/lib # -f technically only required for reruns or failed script, but does # no harm. I don't have kmod source handy, so I can't tell if it will take an overide in the same way. If it will, anything installing to /usr/lib/pkgconfig should be sane enough to create the directory if not already present. Or, for the /lib/pkgconfig symlink, did you all agree to merge everything into /usr while I was offline :-) ? ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
