On Thu, 2013-03-28 at 19:41 +0000, Matt Burgess wrote: > On Thu, 2013-03-28 at 19:47 +0100, Armin K. wrote: > > > FYI, there's --disable-install-libiberty configure option - no need for > > seds to prevent its installation. > > Well spotted. I'm testing a build with that in now.
And it doesn't appear to do what it claims. These are from jhalfs logs of installed files: $ grep libiberty binutils gcc binutils:/usr/include/libiberty.h 24516 root:root 644 binutils:/usr/lib/libiberty.a 1658656 root:root 644 gcc:/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.0/plugin/include/libiberty.h 24516 root:root 644 gcc:/usr/lib/libiberty.a 1717204 root:root 644 To be fair, the './configure --help' output for this switch only claims to disable the installation of the headers for end users. It is libiberty.texi that mentions the archive library: Passing --enable-install-libiberty to the configure script when building libiberty causes the header files and archive library to be installed when make install is run. This option also takes an (optional) argument to specify the installation location, in the same manner as --prefix. Now, that last bit is interesting; we could try '--enable-install-libiberty=/tmp' then just clean up /tmp post-install, but whether that's any easier/clearer than the sed we have is debatable. Open to thoughts. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
