1 | $Id$
|
---|
2 |
|
---|
3 | 1. INTRODUCTION::
|
---|
4 |
|
---|
5 | This collection of scripts, known as jhalfs, strives to create
|
---|
6 | accurate makefiles from the Linux From Scratch book series XML files.
|
---|
7 | This software is an evolution of the original "jhalfs-0.2" code.
|
---|
8 |
|
---|
9 | The usage of this script assumes you have read and are familiar with
|
---|
10 | the book(s) and, therefore, the configuration variables found in config
|
---|
11 | files will have meaning to you. There are a number of command line switches
|
---|
12 | which, if used, will override the config file settings.
|
---|
13 |
|
---|
14 | NOTES::
|
---|
15 | *. The resulting Makefile takes considerable time to run to completion.
|
---|
16 | Lay in a supply of caffeine beverages.
|
---|
17 |
|
---|
18 | *. It is recommended that you temporarily unpack your linux kernel,
|
---|
19 | run <make menuconfig>, configure the kernel as per the book and save
|
---|
20 | the resulting .config file. This suggestion also applies to the
|
---|
21 | configuration of the uClibc package when building a HLFS system using
|
---|
22 | uClibc rather than glibc.
|
---|
23 |
|
---|
24 | 2. INSTALLATION::
|
---|
25 | No installation is required. System-wide installation is not allowed
|
---|
26 | for now.
|
---|
27 |
|
---|
28 | 3. CONFIGURATION FILES::
|
---|
29 | Each book in the LFS series has its own set of configurable parameters
|
---|
30 | as well as the common parameters file.
|
---|
31 |
|
---|
32 | 4. RUNNING::
|
---|
33 | The script master.sh cannot be invoked directly but only via the
|
---|
34 | supplied symlinks. After editing the config file for the project you wish
|
---|
35 | to build, run the script.
|
---|
36 |
|
---|
37 | IMPORTANT:
|
---|
38 | If you use the switch -M (automatically run the generated makefile) you
|
---|
39 | must be 'root' or you can run the scripts using 'sudo'
|
---|
40 | i.e. sudo ./lfs -G -M
|
---|
41 |
|
---|
42 | If you want to run make manually you can only do so if you are 'root' or
|
---|
43 | via 'sudo'
|
---|
44 | i.e (from within the jhalfs directory) sudo make
|
---|
45 |
|
---|
46 | The term <symlink> refers to the 1 of 3 package symlinks, lfs,hlfs,clfs.
|
---|
47 | Replace <symlink> with your choice of packages; i.e.: ./lfs
|
---|
48 |
|
---|
49 | ./<symlink> eg: ./lfs or ./hlfs
|
---|
50 | Create a makefile based on the settings found in the config files.
|
---|
51 | You must enter the build partition/jhalfs directory and manually run <make>
|
---|
52 |
|
---|
53 | ./<symlink> -G eg: ./lfs -G
|
---|
54 | Download the packages and patches necessary to build <symlink>
|
---|
55 |
|
---|
56 | ./<symlink> -G -M eg: ./lfs -G -M
|
---|
57 | Download the packages, create and automatically run the Makefile
|
---|
58 |
|
---|
59 | ./<symlink> --help eg: ./lfs --help
|
---|
60 | will give you a context sensitive list of command line switches.
|
---|
61 |
|
---|
62 | >>>> an expanded example
|
---|
63 |
|
---|
64 | export SRC_ARCHIVE=/mnt/SourceFiles
|
---|
65 |
|
---|
66 | ./lfs -D /mnt/partition4 \
|
---|
67 | -K ~/jhalfs_configs/linux-2.6.16.19-LFS.config \
|
---|
68 | -F ~/jhalfs-configs/fstab-sda3 \
|
---|
69 | -G -T 0 -M
|
---|
70 |
|
---|
71 | explanation:::
|
---|
72 |
|
---|
73 | export SRC_ARCHIVE=/mnt/SourceFiles
|
---|
74 | # This points to a local archive of existing packages. If the version in
|
---|
75 | the archive is incorrect jhalfs will access the net and download the
|
---|
76 | necessary version and store it here for later use. DO NOT set this to
|
---|
77 | $BUILDDIR/sources. If you do not set this variable to a valide directory
|
---|
78 | ALL package tarballs will be downloaded from the 'net.
|
---|
79 |
|
---|
80 | -D /mnt/partition4
|
---|
81 | # where everything takes place. ..NOTE it must already exist and be mounted
|
---|
82 |
|
---|
83 | -K ~/jhalfs_configs/linux-2.6.16.19-LFS.config
|
---|
84 | # If you want to automatically build a the kernel you MUST supply a valid
|
---|
85 | kernel configuration file. The file you supply will be copied and renamed.
|
---|
86 |
|
---|
87 | -F ~/jhalfs-configs/fstab-sda3
|
---|
88 | # If you have a fstab file you wish to use it will be copied and renamed
|
---|
89 |
|
---|
90 | -G # Retrieve the package files. You MUST enable this flag at least once if you
|
---|
91 | wish to do a build or whenever you update the book.
|
---|
92 |
|
---|
93 | -T 0 # don't run any testsuites
|
---|
94 |
|
---|
95 | -M # automatically run make against Makefile once jhalfs finishes its work.
|
---|
96 |
|
---|
97 |
|
---|
98 | 5. LAYOUT::
|
---|
99 |
|
---|
100 | /CLFS/config
|
---|
101 | /master.sh
|
---|
102 | /xxxx.xsl
|
---|
103 |
|
---|
104 | /HLFS/config
|
---|
105 | /master.sh
|
---|
106 | /xxxx.xsl
|
---|
107 |
|
---|
108 | /LFS/config
|
---|
109 | / master.sh
|
---|
110 | /xxxx.xsl
|
---|
111 |
|
---|
112 | /common/config
|
---|
113 | /common_functions
|
---|
114 | /makefile_functions
|
---|
115 | /func_check_versions.sh
|
---|
116 | /func_validate_configs.sh
|
---|
117 |
|
---|
118 | /contrib/jhalfs-paco.patch
|
---|
119 |
|
---|
120 | /extras/do_copy_files
|
---|
121 | /do_ica_prep
|
---|
122 | /do_ica_work
|
---|
123 | /farce
|
---|
124 | /filelist
|
---|
125 |
|
---|
126 | README
|
---|
127 | README.PACO
|
---|
128 | TODO
|
---|
129 |
|
---|
130 | ./clfs ---|
|
---|
131 | ./hlfs ---|+---> master.sh
|
---|
132 | ./lfs ---|
|
---|
133 |
|
---|
134 |
|
---|
135 | 6. FAQ::
|
---|
136 | Q. "It doesn't work!"
|
---|
137 | A. Yes it does, try ./lfs --help
|
---|
138 |
|
---|
139 | Q. "It still doesn't work"
|
---|
140 | A. jhalfs was designed to work against the developement versions of the LFS
|
---|
141 | series of books. Consequently changes in a book(s) sometimes breaks older
|
---|
142 | versions of jhalfs. Before you start pulling out your hair download the
|
---|
143 | latest version of jhalfs is see it that solves your problem.
|
---|
144 |
|
---|
145 | Q. "How do I specify the build location?"
|
---|
146 | A. The original LFS document worked against the well know location /mnt/lfs.
|
---|
147 | This script automates the build of all of the LFS series of books and uses
|
---|
148 | a generic location $BUILDDIR with a default value a /mnt/build_dir.
|
---|
149 | You may change this value to suit your needs.
|
---|
150 |
|
---|
151 | The layout below $BUILDDIR is as follows.
|
---|
152 | $BUILDDIR/
|
---|
153 | jhalfs (makefile,cmd scripts,logs..etc)
|
---|
154 | sources (where packages reside)
|
---|
155 | tools (temporary bootstrap system)
|
---|
156 | cross-tools (temporary CLFS only)
|
---|
157 | ...
|
---|
158 | FHS dir structure
|
---|
159 | ...
|
---|
160 |
|
---|
161 | Q. "What is the function of the SRC_ARCHIVE variable?"
|
---|
162 | A. When then symlinked master.sh runs it creates a local copy of the
|
---|
163 | necessary packages in BUILDDIR/sources by downloading the files. If
|
---|
164 | the variable SRC_ARCHIVE is defined the software will first look in
|
---|
165 | this location for the file and, if found, will copy it to BUILDDIR/sources.
|
---|
166 | If the files are not found in SRC_ARCHIVE _and_ you have write priv to
|
---|
167 | the directory any downloaded files will be mirrored there.
|
---|
168 |
|
---|
169 | Q. "How do I set the SRC_ARCHIVE location?"
|
---|
170 | A. The best way to set the value of SRC_ARCHIVE is
|
---|
171 | export SRC_ARCHIVE=/wherever/you/store/downloaded/packages
|
---|
172 | OR
|
---|
173 | you can change the setting in .common/config.
|
---|
174 |
|
---|
175 | Q. "Why have 2 copies of the files?"
|
---|
176 | A. The package files must be visible during the chroot phase and this is a
|
---|
177 | simple and reliable method of doing so. This method also handles the CLFS
|
---|
178 | build method where the final build may be done on a separate machine.
|
---|
179 |
|
---|
180 | Q. "When I try to build 'xxx' with clfs the makefile fails at the mid-point"
|
---|
181 | A. There could be numerous reasons for the failure but the most likely reason
|
---|
182 | is you are doing a cross-build using the 'chroot' method and the target is
|
---|
183 | not compatible with the host. If you choose to build using the chroot
|
---|
184 | method a test is performed at the end of the temptools phase. If the test
|
---|
185 | succeeds the build continues inside a chroot jail. However if the test fails
|
---|
186 | it means the host and target are not compatible an you should use the
|
---|
187 | 'boot' method to create your target code.
|
---|
188 | As an extreme example: You can build a sparc target on a x86 platform but
|
---|
189 | only the temptools phase. You must run ./clfs using the 'boot' method and
|
---|
190 | not the 'chroot.' You must transfer the toolchain to a sparc platform, reboot
|
---|
191 | the sparc box and continue the build.
|
---|
192 | Of all the LFS series of books the Cross-LFS requires the greatest
|
---|
193 | understanding of host/target hardware combination. Please read the book
|
---|
194 | carefully and don't skip the easy parts (there are none..)
|
---|
195 |
|
---|
196 |
|
---|
197 |
|
---|
198 | Authors:
|
---|
199 | George Boudreau
|
---|
200 | Manuel Canales Esparcia
|
---|
201 | Jeremy Huntwork
|
---|