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
12.2
12.2-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
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/loongarch-12.2
xry111/mips64el
xry111/multilib
xry111/pip3
xry111/rust-wip-20221008
xry111/update-glibc
Rev | Line | |
---|
[0b74af3] | 1 | <sect1 id="ch02-aboutsbus">
|
---|
| 2 | <title>About SBUs</title>
|
---|
| 3 | <?dbhtml filename="aboutsbus.html" dir="chapter02"?>
|
---|
| 4 |
|
---|
| 5 | <para>SBUs are <emphasis>Static Bash Units</emphasis> and they are our way
|
---|
| 6 | of identifying how long a package takes to compile. Why don't we use normal
|
---|
| 7 | times like anybody else?</para>
|
---|
| 8 |
|
---|
[1e6acd6] | 9 | <para>The biggest problem is that times cannot be accurate, not even a
|
---|
[0b74af3] | 10 | little bit. So many people install LFS on so many different systems, the
|
---|
| 11 | times it takes to compile something varies too much. One package may take
|
---|
[00d4d2b] | 12 | 20 minutes on one system, but that same package may take 3 days on another
|
---|
[0b74af3] | 13 | (this is not an exaggeration). So instead we've come up with a
|
---|
| 14 | <emphasis>Static Bash Unit</emphasis> or <emphasis>SBU</emphasis>.</para>
|
---|
| 15 |
|
---|
| 16 | <para>It works like this: the very first package you compile in this book
|
---|
[26e62aa] | 17 | is Bash in Chapter 5 and it'll be statically linked. The time it takes to
|
---|
[0b74af3] | 18 | compile this package will be the basis and called the SBU. All other
|
---|
| 19 | compile times are relative to the time it takes to install Bash. For
|
---|
[3998446] | 20 | example, GCC-3.2 takes about 9.5 SBUs and it's proven that this number is
|
---|
[0b74af3] | 21 | fairly consistent among a lot of different systems. So multiply 9.5 by the
|
---|
| 22 | number of seconds it takes for Bash to install (the SBU value) and you get
|
---|
| 23 | a close approximation of how long GCC will take on your system.</para>
|
---|
| 24 |
|
---|
[1e6acd6] | 25 | <para>Note: We've seen that SBUs don't work well on SMP based machines. So
|
---|
| 26 | all bets are off if you're lucky enough to have an SMP setup.</para>
|
---|
[0b74af3] | 27 |
|
---|
| 28 | </sect1>
|
---|
| 29 |
|
---|
Note:
See
TracBrowser
for help on using the repository browser.