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_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
| Line | |
|---|
| 1 | <sect2>
|
|---|
| 2 | <title>Command explanations</title>
|
|---|
| 3 |
|
|---|
| 4 | <para><userinput>patch -Np1 -i
|
|---|
| 5 | ../ncurses-&ncurses-version;-patch:</userinput> This patch fixes a compile
|
|---|
| 6 | problem with GCC-3.2 because Ncurses uses constructions that are no longer
|
|---|
| 7 | valid in the new C++ standard.</para>
|
|---|
| 8 |
|
|---|
| 9 | <para><userinput>--with-shared:</userinput> This enables the build of the
|
|---|
| 10 | shared ncurses library files.</para>
|
|---|
| 11 |
|
|---|
| 12 | <para><userinput>mv /lib/*.a /usr/lib :</userinput> This
|
|---|
| 13 | moves all of the static ncurses library files from /lib to /usr/lib.
|
|---|
| 14 | /lib should only contain the shared files which are essential to the
|
|---|
| 15 | system when /usr may not be mounted.</para>
|
|---|
| 16 |
|
|---|
| 17 | <para><userinput>chmod 755 *.5.2:</userinput> Shared libraries should be
|
|---|
| 18 | executable. Ncurses install routine doesn't set the permissions
|
|---|
| 19 | properly so we do it manually instead.</para>
|
|---|
| 20 |
|
|---|
| 21 | <para><userinput>ln -sf libncurses.a libcurses.a:</userinput> Some
|
|---|
| 22 | programs try to link using -lcurses instead of -lncurses. This symlink
|
|---|
| 23 | ensures that such programs will link without errors.</para>
|
|---|
| 24 |
|
|---|
| 25 | <para><userinput>ln -sf ../../lib/libncurses.so etc:</userinput> These
|
|---|
| 26 | symlinks are created to tidy up the installation. It's good practice to
|
|---|
| 27 | have the *.so files in /usr/lib as well as in /lib, to ensure that the
|
|---|
| 28 | linker is always able to find the files whether it's looking in /lib or
|
|---|
| 29 | /usr/lib.</para>
|
|---|
| 30 |
|
|---|
| 31 | </sect2>
|
|---|
| 32 |
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
