[lfs] branch multilib updated: Chapter 8 (ML): Don't include stripping.

This is an automated email from the git hooks/post-receive script.

git pushed a commit to branch multilib
in repository lfs.

The following commit(s) were added to refs/heads/multilib by this push:
     new d046db99c Chapter 8 (ML): Don't include stripping.
d046db99c is described below

commit d046db99cc7afafbf6e7fe79498121d43ee5b48f
Author: Zeckmathederg <[email protected]>
AuthorDate: Wed May 13 18:08:19 2026 -0600

    Chapter 8 (ML): Don't include stripping.
    
    On the surface, this seems like a pretty bad idea. However, there's a
    few reasons why I have decided to no longer include stripping
    instructions.
    
    For one, including both lib and lib32 instructions for stripping is
    really convuluted without repeating a bunch of instructions. While this
    could just include instructions for lib, it wouldn't be quite complete.
    
    Secondly, it alters ld-linux, which can be a bad thing. With the
    previous point, this can cause bad things to happen, namely execution
    problems and symlink issues.
    
    Thirdly is that stripping in general can cause segfaults and other
    behavior. MLFS is often used for binary-only software, so it's best to
    provide libraries that won't later cause issues because of stripping.
    
    I think the BLFS stripping instructions are better suited for this.
    
    I never strip as a precaution since I also use LFS and want a stable
    platform.
    
    The current instructions were dangerous to the system as it breaks lib32
    ld-linux. The fix is generally easy, it's a copying issue.
    
    Until I resolve it as I'm unable to right now, the stripping
    instructions will take a back seat so users don't break their systems.
    Once I get time, this should be coming back. Right now, I'm trying to
    upgrade to GCC-16.1.0 + OpenSSL-4.0.0 and want to get my main system in
    a good state. I need to verify GLFS+SLFS is sane before I start
    experimenting with the stripping instructions.
    
    I have a few ideas on how to make the instructions safe, but the main
    thing is time, testing, and patience.
---
 chapter08/chapter08.xml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/chapter08/chapter08.xml b/chapter08/chapter08.xml
index 868de69d0..5c1182ecf 100644
--- a/chapter08/chapter08.xml
+++ b/chapter08/chapter08.xml
@@ -115,8 +115,10 @@
   <!-- sysv -->
   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="sysvinit.xml"/>
 
+<!-- NOT SUPPORTED
   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="aboutdebug.xml"/>
   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="stripping.xml"/>
+-->
   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="cleanup.xml"/>
 
 </chapter>

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.

-- 
http://lists.linuxfromscratch.org/sympa/info/lfs-book
Unsubscribe: See the above information page