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 | <sect1 id="ch02-download">
|
|---|
| 2 | <title>How to download the software</title>
|
|---|
| 3 | <?dbhtml filename="download.html" dir="chapter02"?>
|
|---|
| 4 |
|
|---|
| 5 | <para>Throughout this document, we will assume that all the
|
|---|
| 6 | packages that were downloaded are placed somewhere in $LFS/usr/src.</para>
|
|---|
| 7 |
|
|---|
| 8 | <para>While it doesn't matter at all where you save the downloaded
|
|---|
| 9 | packages, we recommend storing it at least on the LFS partition. This just
|
|---|
| 10 | makes sense because you would still have access to those files when you boot
|
|---|
| 11 | into the LFS system. $LFS/usr/src is just a logical place to store source
|
|---|
| 12 | code, but by no means a requirement. You may even want to create a
|
|---|
| 13 | subdirectory under $LFS/usr/src for tarball storage. That way you can
|
|---|
| 14 | separate tarballs from temporary build directories, but again that's up
|
|---|
| 15 | to you.</para>
|
|---|
| 16 |
|
|---|
| 17 | <para>The next chapter contains a list of all the packages that need to be
|
|---|
| 18 | downloaded. The LFS partition isn't created yet, so you can't store it
|
|---|
| 19 | there yet. Just save it elsewhere for now, and when the LFS partition is
|
|---|
| 20 | created, move them over.</para>
|
|---|
| 21 |
|
|---|
| 22 | </sect1>
|
|---|
| 23 |
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
