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 | The term <symlink> refers to the 1 of 3 package symlinks, lfs,hlfs,clfs.
|
---|
38 | Replace <symlink> with your choice of packages; i.e.: ./lfs
|
---|
39 |
|
---|
40 | ./<symlink> eg: ./lfs or ./hlfs
|
---|
41 | Create a makefile based on the settings found in the config files.
|
---|
42 | You must enter the build partition/jhalfs directory and manually run <make>
|
---|
43 |
|
---|
44 | ./<symlink> -G eg: ./lfs -G
|
---|
45 | Download the packages and patches necessary to build <symlink>
|
---|
46 |
|
---|
47 | ./<symlink> -G -M eg: ./lfs -G -M
|
---|
48 | Download the packages, create and automatically run the Makefile
|
---|
49 |
|
---|
50 | ./<symlink> --help eg: ./lfs --help
|
---|
51 | will give you a context sensitive list of command line switches.
|
---|
52 |
|
---|
53 | 5. LAYOUT::
|
---|
54 |
|
---|
55 | /CLFS/config
|
---|
56 | /master.sh
|
---|
57 | /xxxx.xsl
|
---|
58 |
|
---|
59 | /HLFS/config
|
---|
60 | /master.sh
|
---|
61 | /xxxx.xsl
|
---|
62 |
|
---|
63 | /LFS/config
|
---|
64 | / master.sh
|
---|
65 | /xxxx.xsl
|
---|
66 |
|
---|
67 | /common/config
|
---|
68 | /common_functions
|
---|
69 | /makefile_functions
|
---|
70 | /func_check_versions.sh
|
---|
71 | /func_validate_configs.sh
|
---|
72 |
|
---|
73 | /contrib/jhalfs-paco.patch
|
---|
74 |
|
---|
75 | /extras/do_copy_files
|
---|
76 | /do_ica_prep
|
---|
77 | /do_ica_work
|
---|
78 | /farce
|
---|
79 | /filelist
|
---|
80 |
|
---|
81 | README
|
---|
82 | README.PACO
|
---|
83 | TODO
|
---|
84 |
|
---|
85 | ./clfs ---|
|
---|
86 | ./hlfs ---|+---> master.sh
|
---|
87 | ./lfs ---|
|
---|
88 |
|
---|
89 |
|
---|
90 | 6. FAQ::
|
---|
91 | Q. "It doesn't work!"
|
---|
92 | A. Yes it does, try ./lfs --help
|
---|
93 |
|
---|
94 | Q. "How do I specify the build location?"
|
---|
95 | A. The original LFS document worked against the well know location /mnt/lfs.
|
---|
96 | This script automates the build of all of the LFS series of books and uses
|
---|
97 | a generic location $BUILDDIR with a default value a /mnt/build_dir.
|
---|
98 | You may change this value to suit your needs.
|
---|
99 |
|
---|
100 | The layout below $BUILDDIR is as follows.
|
---|
101 | $BUILDDIR/
|
---|
102 | jhalfs (makefile,cmd scripts,logs..etc)
|
---|
103 | sources (where packages reside)
|
---|
104 | tools (temporary bootstrap system)
|
---|
105 | cross-tools (temporary CLFS only)
|
---|
106 | ...
|
---|
107 | FHS dir structure
|
---|
108 | ...
|
---|
109 |
|
---|
110 | Q. "What is the function of the SRC_ARCHIVE variable?"
|
---|
111 | A. When then symlinked master.sh runs it creates a local copy of the
|
---|
112 | necessary packages in BUILDDIR/sources by downloading the files. If
|
---|
113 | the variable SRC_ARCHIVE is defined the software will first look in
|
---|
114 | this location for the file and, if found, will copy it to BUILDDIR/sources.
|
---|
115 | If the files are not found in SRC_ARCHIVE _and_ you have write priv to
|
---|
116 | the directory any downloaded files will be mirrored there.
|
---|
117 |
|
---|
118 | Q. "How do I set the SRC_ARCHIVE location?"
|
---|
119 | A. The best way to set the value of SRC_ARCHIVE is
|
---|
120 | export SRC_ARCHIVE=/wherever/you/store/downloaded/packages
|
---|
121 | OR
|
---|
122 | you can change the setting in .common/config.
|
---|
123 |
|
---|
124 | Q. "Why have 2 copies of the files?"
|
---|
125 | A. The package files must be visible during the chroot phase and this is a
|
---|
126 | simple and reliable method of doing so. This method also handles the CLFS
|
---|
127 | build method where the final build may be done on a separate machine.
|
---|
128 |
|
---|
129 | Authors:
|
---|
130 | George Boudreau
|
---|
131 | Manuel Canales Esparcia
|
---|
132 | Jeremy Huntwork
|
---|