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
| 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
|
|---|
| 5 | applied. This patch is needed to avoid a conflict of variable names with
|
|---|
| 6 | certain Glibc versions (usually glibc-2.1.x) when compiling sh-utils
|
|---|
| 7 | statically. It is however safe to apply the patch even if you are running
|
|---|
| 8 | a different glibc version. So, if you aren't sure, it's best to apply
|
|---|
| 9 | it.</para>
|
|---|
| 10 |
|
|---|
| 11 | <para><screen><userinput>patch -Np1 -i ../sh-utils-&sh-utils-version;.patch</userinput></screen></para>
|
|---|
| 12 |
|
|---|
| 13 | <para>Install Sh-utils by running the following commands:</para>
|
|---|
| 14 |
|
|---|
| 15 | <para><screen><userinput>LDFLAGS="-static" ./configure --prefix=$LFS/static \
|
|---|
| 16 | --disable-nls &&
|
|---|
| 17 | make &&
|
|---|
| 18 | make install</userinput></screen></para>
|
|---|
| 19 |
|
|---|
| 20 | <para>During the make install stage you will see the following warning:</para>
|
|---|
| 21 |
|
|---|
| 22 | <blockquote><screen>WARNING: insufficient access; not installing su
|
|---|
| 23 | NOTE: to install su, run 'make install-root' as root</screen></blockquote>
|
|---|
| 24 |
|
|---|
| 25 | <para>You can safely ignore that warning. You need to be logged in as root
|
|---|
| 26 | in order to install su the way Sh-utils wants to install it, which is being
|
|---|
| 27 | suid root. Because we don't need su during Chapter 6, and su will be properly
|
|---|
| 28 | installed when we re-install Sh-utils in Chapter 6, you can just
|
|---|
| 29 | pretend you didn't see it.</para>
|
|---|
| 30 |
|
|---|
| 31 | </sect2>
|
|---|
| 32 |
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
