Ignore:
Timestamp:
08/02/2013 11:56:29 PM (11 years ago)
Author:
Bruce Dubbs <bdubbs@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
5552483f
Parents:
c4b0455
Message:

Added sections on stripping and removing .la files to
Notes on Buiiding Software in the Introduction.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@11569 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:
1 edited

Legend:

Unmodified
Added
Removed
  • introduction/important/building-notes.xml

    rc4b0455 r3c31062  
    360360  </sect2>
    361361
     362  <sect2 id="stripping">
     363    <title>Stripping One More Time</title>
     364
     365    <para>In LFS, stripping of debugging symbols was discussed a couple of
     366    times.  When building BLFS packages, there are generally no special
     367    instructions that discuss stripping again.  It is probably not a good
     368    idea to strip an executable or a library while it is in use, so exiting
     369    any windowing environment is a good idea.  Then you can do:</para>
     370
     371    <screen><userinput>find /{,usr/}{bin,lib,sbin} -type f -exec strip --strip-unneeded {} \;</userinput></screen>
     372   
     373    <para>If you install programs in other directories such as /opt or /usr/local,
     374    you may want to strip the files there too.</para>
     375
     376    <para>For more information on stripping, see <ulink
     377    url="http://www.technovelty.org/linux/stripping-shared-libraries.html"/>.</para>
     378
     379  </sect2>
     380
     381  <sect2 id="libtool">
     382    <title>Libtool files</title>
     383
     384    <para>One of the side effects of packages that use Autotools, including
     385    libtool, is that they create many files with an .la extention.  These
     386    files are not needed in an LFS environment.  If there are conflicts with
     387    pkgconfig entries, they can actually prevent successful builds.  You
     388    may want to consider removing these files periodically:</para>
     389
     390    <screen><userinput>find /lib /usr/lib -name \*.la -delete</userinput></screen>
     391   
     392  </sect2>
     393
    362394</sect1>
Note: See TracChangeset for help on using the changeset viewer.