Alice Wonder wrote: > grep "tmp2" /mnt/lfs/usr/lib64/*.la > /mnt/lfs/usr/lib64/libbfd.la:dependency_libs=' > -L/tmp2/build/binutils-build/bfd/../libiberty/pic -liberty -lz' > /mnt/lfs/usr/lib64/libopcodes.la:dependency_libs=' > -L/tmp2/build/binutils-build/opcodes/../libiberty/pic -liberty' > > /tmp2 is where I did the chapter 6 build (tmpfs) > > The two libtool files installed from binutils are tainted with the build > directory. > > I don't know that it causes any problems but it probably should be > fixed.
I suppose it should be fixed, but it makes no difference. Both of those files have -L which only adds a search library when building a dependent package. The libraries that it needs are in /usr/lib and we instruct users to delete build directories like binutils-build after the build is complete. It looks like it is pulled into /usr/lib/cairo/libcairo-trace.la within BLFS too. Looking at the binutils logs, I see /bin/sh ./libtool --mode=install /tools/bin/install -c libbfd.la '/usr/lib' ... libtool: install: /tools/bin/install -c .libs/libbfd.lai /usr/lib/libbfd.la But there are no messages about where libbfd.lai comes from. The same thing happens with libopcodes.lai. There are a couple of ways to fix this. The easiest would be a sed removing the -L entry completely from these files. Another easy thing to do is just remove all the /usr/lib/*.la files. They are not needed on LFS systems. I did find this in opcodes/Makefile.am: # It's desirable to list ../bfd/libbfd.la in DEPENDENCIES and LIBADD. # Unfortunately this causes libtool to add -L$(libdir), referring to the # planned install directory of libbfd. This can cause us to pick up an # old version of libbfd, or to pick up libbfd for the wrong architecture # if host != build. So for building with shared libraries we use a # hardcoded path to libbfd.so instead of relying on the entries in libbfd.la. libopcodes_la_DEPENDENCIES = $(OFILES) @SHARED_DEPENDENCIES@ -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
