Automatic merge of trunk into multilib

This commit is contained in:
Thomas Trepl (Moody) 2022-10-11 00:30:07 +02:00
commit 32f686fa8d
2 changed files with 14 additions and 11 deletions

View File

@ -17,7 +17,7 @@ $regex[ 'intltool' ] = "/^.*Latest version is (\d[\d\.]+\d).*$/";
$regex[ 'less' ] = "/^.*current released version is less-(\d+).*$/"; $regex[ 'less' ] = "/^.*current released version is less-(\d+).*$/";
$regex[ 'mpfr' ] = "/^mpfr-([\d\.]+)\.tar.*$/"; $regex[ 'mpfr' ] = "/^mpfr-([\d\.]+)\.tar.*$/";
$regex[ 'Python' ] = "/^.*Latest Python 3.*Python (3[\d\.]+\d).*$/"; $regex[ 'Python' ] = "/^.*Latest Python 3.*Python (3[\d\.]+\d).*$/";
$regex[ 'systemd' ] = "/^.*v([\d]+)$/"; $regex[ 'systemd' ] = "/^.*systemd v([\d]+)$/";
//$regex[ 'sysvinit' ] = "/^.*sysvinit-([\d\.]+)dsf\.tar.*$/"; //$regex[ 'sysvinit' ] = "/^.*sysvinit-([\d\.]+)dsf\.tar.*$/";
$regex[ 'tzdata' ] = "/^.*tzdata([\d]+[a-z]).*$/"; $regex[ 'tzdata' ] = "/^.*tzdata([\d]+[a-z]).*$/";
$regex[ 'xz' ] = "/^.*xz-([\d\.]*\d).*$/"; $regex[ 'xz' ] = "/^.*xz-([\d\.]*\d).*$/";

View File

@ -300,12 +300,11 @@
its library search order. Detailed information can be obtained from its library search order. Detailed information can be obtained from
<command>ld</command> by passing it the <parameter>--verbose</parameter> <command>ld</command> by passing it the <parameter>--verbose</parameter>
flag. For example, <command>$LFS_TGT-ld --verbose | grep SEARCH</command> flag. For example, <command>$LFS_TGT-ld --verbose | grep SEARCH</command>
will illustrate the current search paths and their order. It shows which will illustrate the current search paths and their order. Note that this
files are linked by <command>ld</command> by compiling a dummy program and example can be run as shown only while being user
passing the <parameter>--verbose</parameter> switch to the linker. For <systemitem class="username">lfs</systemitem>. If you come back to this
example, page later, replace <command>$LFS_TGT-ld</command> with just
<command>$LFS_TGT-gcc dummy.c -Wl,--verbose 2&gt;&amp;1 | grep succeeded</command> <command>ld</command>.</para>
will show all the files successfully opened during the linking.</para>
<para>The next package installed is gcc. An example of what can be <para>The next package installed is gcc. An example of what can be
seen during its run of <command>configure</command> is:</para> seen during its run of <command>configure</command> is:</para>
@ -318,14 +317,18 @@ checking what linker to use... /mnt/lfs/tools/i686-lfs-linux-gnu/bin/ld</compute
directories to find which tools to use. However, during the actual directories to find which tools to use. However, during the actual
operation of <command>gcc</command> itself, the same search paths are not operation of <command>gcc</command> itself, the same search paths are not
necessarily used. To find out which standard linker <command>gcc</command> necessarily used. To find out which standard linker <command>gcc</command>
will use, run: <command>$LFS_TGT-gcc -print-prog-name=ld</command>.</para> will use, run: <command>$LFS_TGT-gcc -print-prog-name=ld</command>. Again,
remove the <command>$LFS_TGT-</command> part if coming back to this
later.</para>
<para>Detailed information can be obtained from <command>gcc</command> by <para>Detailed information can be obtained from <command>gcc</command> by
passing it the <parameter>-v</parameter> command line option while compiling passing it the <parameter>-v</parameter> command line option while compiling
a dummy program. For example, <command>gcc -v dummy.c</command> will show a program. For example, <command>$LFS_TGT-gcc -v
<replaceable>example.c</replaceable></command> (or without <command>
$LFS_TGT-</command> if coming back later to this) will show
detailed information about the preprocessor, compilation, and assembly detailed information about the preprocessor, compilation, and assembly
stages, including <command>gcc</command>'s included search paths and their stages, including <command>gcc</command>'s search paths for included
order.</para> headers and their order.</para>
<para>Next installed are sanitized Linux API headers. These allow the <para>Next installed are sanitized Linux API headers. These allow the
standard C library (glibc) to interface with features that the Linux standard C library (glibc) to interface with features that the Linux