[lfs] 01/02: gcc-pass1: simplify the instruction generating limits.h

"Git Owner" ([email protected] via lfs-book Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.book
Message-ID <[email protected]>
This is an automated email from the git hooks/post-receive script.

git pushed a commit to branch trunk
in repository lfs.

commit c79e4d3941175e86066464652778b36e8ee540c2
Author: Xi Ruoyao <[email protected]>
AuthorDate: Sat May 9 16:04:02 2026 +0800

    gcc-pass1: simplify the instruction generating limits.h
---
 chapter05/gcc-pass1.xml | 13 ++-----------
 1 file changed, 2 insertions(+), 11 deletions(-)

diff --git a/chapter05/gcc-pass1.xml b/chapter05/gcc-pass1.xml
index 24fd9f576..c73815686 100644
--- a/chapter05/gcc-pass1.xml
+++ b/chapter05/gcc-pass1.xml
@@ -225,17 +225,8 @@ cd       build</userinput></screen>
     header using a command that is identical to what the GCC build system does
     in normal circumstances:</para>
 
-    <note>
-      <para>The command below shows an example of nested command substitution
-      using two methods: backquotes and a <literal>$()</literal> construct. 
-      It could be rewritten using the same method for both substitutions,
-      but is shown this way to demonstrate how they can be mixed.  Generally
-      the <literal>$()</literal> method is preferred.</para>
-    </note>
-
-<screen><userinput remap="install">cd ..
-cat gcc/limitx.h gcc/glimits.h gcc/limity.h > \
-  `dirname $($LFS_TGT-gcc -print-libgcc-file-name)`/include/limits.h</userinput></screen>
+<screen><userinput remap="install">cat ../gcc/{limitx,glimits,limity}.h  > \
+  $($LFS_TGT-gcc -print-file-name=include)/limits.h</userinput></screen>
   </sect2>
 
   <sect2 role="content">

-- 
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.