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
| Line | |
|---|
| 1 | <sect2>
|
|---|
| 2 | <title>Command explanations</title>
|
|---|
| 3 |
|
|---|
| 4 | <para>
|
|---|
| 5 | <userinput>--with-local-prefix:</userinput> GCC installs a number of
|
|---|
| 6 | files in /usr/local even when --prefix is set to something else. We
|
|---|
| 7 | don't want that to happen in this case so that's why we use the
|
|---|
| 8 | --with-local-prefix option to change that path.
|
|---|
| 9 | </para>
|
|---|
| 10 |
|
|---|
| 11 | <para>
|
|---|
| 12 | <userinput>--with-gxx-include-dir:</userinput> GCC installs the C++
|
|---|
| 13 | header files in /usr/include/g++ by default. Again, in this case we
|
|---|
| 14 | don't want that to happen, we want this GCC version to be installed
|
|---|
| 15 | completely under /usr/local/gcc2952.
|
|---|
| 16 | </para>
|
|---|
| 17 |
|
|---|
| 18 | <para>
|
|---|
| 19 | <userinput>make bootstrap:</userinput> Compile GCC by bootstrapping it.
|
|---|
| 20 | Here that means the compiler will be built three times in total. First
|
|---|
| 21 | it is compiled with your system's default compiler (which will usually
|
|---|
| 22 | be a gcc or egcs compiler). This is stage 1 compiler. Then GCC will re-compile
|
|---|
| 23 | itself but instead of using your system's compiler it will use itself to
|
|---|
| 24 | compile itself again. This is the stage 2 compiler. Then it will compile
|
|---|
| 25 | itself a second time with the stage 2 compiler and compares the second
|
|---|
| 26 | and the third build to see if they are identical. If so, the
|
|---|
| 27 | compilation was a success.
|
|---|
| 28 | </para>
|
|---|
| 29 |
|
|---|
| 30 | </sect2>
|
|---|
| 31 |
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
