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>tooldir=/usr:</userinput> Normally, the tooldir (the
|
|---|
| 5 | directory where the executables from binutils end up in) is set to
|
|---|
| 6 | $(exec_prefix)/$(target_alias) which expands into, for example,
|
|---|
| 7 | /usr/i686-pc-linux-gnu. Since we only build for our own system, we don't
|
|---|
| 8 | need this target specific directory in /usr. That setup would be used
|
|---|
| 9 | if the system was used to cross-compile (for example
|
|---|
| 10 | compiling a package on the Intel machine that generates code that can be
|
|---|
| 11 | executed on Apple PowerPC machines).</para>
|
|---|
| 12 |
|
|---|
| 13 | <para><userinput>make tooldir=/usr install-info:</userinput> This will
|
|---|
| 14 | install binutil's info pages.</para>
|
|---|
| 15 |
|
|---|
| 16 | </sect2>
|
|---|
| 17 |
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
