Ignore:
Timestamp:
09/06/2021 05:42:49 PM (3 years ago)
Author:
Pierre Labastie <pierre.labastie@…>
Branches:
11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
fef4473
Parents:
7999839
Message:

Remove spaces at the end of lines

I know it is somewhat useless, but I don't like them for
two reasons: first they cannot be seen, and I do not like things I
cannot see. Second, git highlights them, and this is disturbing...

Location:
introduction/important
Files:
2 edited

Legend:

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

    r7999839 r8558044  
    460460      <para>If you did not strip programs and libraries in LFS,
    461461      the following will probably make your system unusable. To avoid that,
    462       run the instructions at <ulink url="&lfs-root;/chapter08/strippingagain.html"/> 
    463       instead.  After the critical files are  stripped using those instructions, 
     462      run the instructions at <ulink url="&lfs-root;/chapter08/strippingagain.html"/>
     463      instead.  After the critical files are  stripped using those instructions,
    464464      the instructions below can be run any time new packages are installed.
    465465      </para>
  • introduction/important/la-files.xml

    r7999839 r8558044  
    3030      this tool are quite dated.  It was intended to manage libraries on
    3131      systems with less advanced capabilities than a modern Linux system.
    32    
     32
    3333    </para>
    3434
     
    4545
    4646    </para>
    47    
     47
    4848    <para>
    4949
     
    5353       in the libraries.  When building a package that uses libtool, the
    5454       process automatically looks for these files.  If a package is updated
    55        and no longer uses the .la file, then the build process can break. 
    56    
     55       and no longer uses the .la file, then the build process can break.
     56
    5757    </para>
    5858
     
    6363       function, lt_dlopen, to load libraries as needed during execution and
    6464       resolve their dependencies at run time.  In this case, the .la files
    65        should remain. 
    66    
     65       should remain.
     66
    6767    </para>
    6868
     
    7171        The script below, removes all unneeded .la files and saves them in a
    7272        directory, /var/local/la-files by default, not in the normal library
    73         path.  It also searches all pkg-config files (.pc) for embedded 
    74         references to .la files and fixes them to be conventional library 
    75         references needed when an application or library is built.  It 
     73        path.  It also searches all pkg-config files (.pc) for embedded
     74        references to .la files and fixes them to be conventional library
     75        references needed when an application or library is built.  It
    7676        can be run as needed to clean up the directories that may be causing
    7777        problems.
    7878
    7979    </para>
    80    
     80
    8181<screen role="root"><userinput>cat &gt; /usr/sbin/remove-la-files.sh &lt;&lt; "EOF"
    8282<literal>#!/bin/bash
     
    109109# Fix any .pc files that may have .la references
    110110
    111 STD_PC_PATH='/usr/lib/pkgconfig 
    112              /usr/share/pkgconfig 
    113              /usr/local/lib/pkgconfig 
     111STD_PC_PATH='/usr/lib/pkgconfig
     112             /usr/share/pkgconfig
     113             /usr/local/lib/pkgconfig
    114114             /usr/local/share/pkgconfig'
    115115
     
    129129        basename=$(basename $word )
    130130        libref=$(echo $basename|sed -e 's/^lib/-l/' -e 's/\.la$//')
    131            
     131
    132132        # Fix the .pc file
    133133        sed -i "s:$word:$libref:" $pc
Note: See TracChangeset for help on using the changeset viewer.