Ignore:
Timestamp:
09/11/2001 07:25:24 PM (23 years ago)
Author:
Gerard Beekmans <gerard@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v3_0, v3_1, v3_2, v3_3, v4_0, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
1265c08
Parents:
87cf4b1
Message:

reworded a bit. make install on debian doesn't fail. The error is
ignored as it should and make's return value is now 0. This may not be
like this on all systems if the 'make' program is older.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1226 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter05/bash-inst.xml

    r87cf4b1 r0e6ea1c  
    4545old version of the texinfo package. This error is not severe by any means: the
    4646info pages will be installed when we recompile bash dynamically in
    47 chapter 6, so you can ignore it. You do, however, have to run the last
    48 two commands manually (the <userinput>cd $LFS/bin</userinput> and
    49 <userinput>ln -sf bash sh</userinput> commands) because they won't be
    50 executed when the error occurs.</para>
     47chapter 6, so you can ignore it.
     48
     49<para>When we tested it with the latest Debian version, the last two
     50commands were executed because the install process didn't return with a
     51value larger than 0. But you would do good to check if you have the
     52<filename class="symlink">$LFS/bin/sh</filename> symlink on your LFS
     53partition. If not, run the last two commands manually now.</para>
    5154
    5255</sect2>
Note: See TracChangeset for help on using the changeset viewer.