source: chapter05/shellutils-inst.xml@ d67368f

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 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
Last change on this file since d67368f was e4b9338, checked in by Gerard Beekmans <gerard@…>, 21 years ago

fix typo's

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

  • Property mode set to 100644
File size: 1.5 KB
Line 
1<sect2>
2<title>Installation of Sh-utils</title>
3
4<para>Before Sh-utils is installed, the sh-utils patch file may need to be
5applied. This patch is needed to avoid a conflict of variable names with
6certain Glibc versions (usually glibc-2.1.x) when compiling sh-utils
7statically. It is however safe to apply the patch even if you are running
8a different glibc version. So, if you aren't sure, it's best to apply
9it.</para>
10
11<para><screen><userinput>patch -Np1 -i ../sh-utils-&sh-utils-version;.patch</userinput></screen></para>
12
13<para>Prepare Sh-utils to be compiled:</para>
14
15<para><screen><userinput>LDFLAGS="-static" ./configure --prefix=$LFS/static \
16&nbsp;&nbsp;&nbsp;&nbsp;--disable-nls</userinput></screen></para>
17
18<para>Continue with compiling the package:</para>
19
20<para><screen><userinput>make</userinput></screen></para>
21
22<para>And finish off installing the package:</para>
23
24<para><screen><userinput>make install</userinput></screen></para>
25
26<para>During the make install stage you will see the following warning:</para>
27
28<blockquote><screen>WARNING: insufficient access; not installing su
29NOTE: to install su, run 'make install-root' as root</screen></blockquote>
30
31<para>You can safely ignore that warning. You need to be logged in as root
32in order to install <filename>su</filename> the way Sh-utils wants to install
33it, which is suid root. Because we don't need <filename>su</filename> during
34Chapter 6, and <filename>su</filename> will be properly installed when we
35re-install Sh-utils in Chapter 6.</para>
36
37</sect2>
38
Note: See TracBrowser for help on using the repository browser.