Changeset 9a865396
- Timestamp:
- 03/08/2012 06:03:56 PM (13 years ago)
- Branches:
- ablfs
- Children:
- 7ea25e4
- Parents:
- 2507cf7
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
README
r2507cf7 r9a865396 84 84 installed in $BLFS_ROOT (default /blfs_root) on the xLFS system, 85 85 and a few dependencies (which you may select) are built at the 86 end of the jhalfs run. The pre-made build dependencies 87 scripts has been written based on a LFS build. For CLFS and HLFS 88 builds you may need to adjust those scripts, that are found into the 89 common/blfs-tool-deps directory in the jhalfs sources tree. 86 end of the jhalfs run, before the custom tools. As of March 8, 2012, 87 works only with LFS. The instructions for building the dependencies 88 are taken from the BLFS book. 90 89 91 90 (TODO: is this relevant to present CLFS?) … … 108 107 109 108 - If you think that you may need the libxml2/libxslt Python modules, 110 remove the libxml2 and libxslt trackin files found in $TRACKING_DIR.109 remove the libxml2 and libxslt entries found in $TRACKING_FILE. 111 110 112 111 - Configure sudo, adding the needed privileges for the user. For -
README.BLFS
r2507cf7 r9a865396 34 34 3. USAGE:: 35 35 36 Due t he complexity of the BLFS book, the scripts and Makefile generation37 is done in several steps:36 Due to the complexity of the BLFS book, the scripts and Makefile 37 generation is done in several steps: 38 38 39 39 3.1 INSTALLED PACKAGES TRACKING SYSTEM:: … … 55 55 The default location of the tracking directory is /var/lib/jhalfs/BLFS. 56 56 NB : after the initial build, that directory is only used to contain 57 instpkg.xml 57 instpkg.xml, unless custom tools have been built. In the latter case, 58 it also contains empty files whose name are $PKG-$VERSION for each 59 versionned package built. The information about those packages is 60 included into instpkg.xml the next time the tool is run. 58 61 59 62 3.2 BLFS_TOOL INSTALLATION:: … … 119 122 you just built xLFS, and you can skip to step 3.4. 120 123 121 To do that run "make update". It may happen that the subversion124 To do that, run "make update". It may happen that the subversion 122 125 version of your building host is older than the version you just 123 126 built. This may generate weird errors like "'.' omitted". The easiest 124 127 thing to do in that case, is to completely remove the blfs-xml directory 125 and run "make update". 128 and run "make update". With recent versions of subversion, you can also 129 run "svn upgrade" from inside the blfs-xml directory. 126 130 127 131 On the next configuration run, packages already installed but listed … … 161 165 of B, then the tree dependency restarts from there, that is with the 162 166 layout B->C->... You may then hit the case B->C->A->C, for which you 163 should answer no, unless you want to enter an infinite (human driven) loop. 167 should answer no, unless you want to enter an infinite (human driven) 168 loop;-) 164 169 165 170 You end up with a book.xml file which contains the linearized book, … … 213 218 Normally, bootscript installation should work. On the other hand, the 214 219 book does not give instruction for running them, so you might have to 215 manually insert /etc/init.d/r d.d/<initscript> at some place during the build.220 manually insert /etc/init.d/rc.d/<initscript> at some place during the build. 216 221 217 222 4.2 PACKAGE CONFIGURATION:: … … 220 225 edit the build script to fit the needs of your system. Sometimes, the 221 226 bash startup files are modified (see for example the instructions for 222 llvm). You might have to insert something like "source /etc/bash_profile"223 at some point during the build.227 llvm). The shipped 'envars.conf' contains a line 'source /etc/profile', 228 which ensures that the proper environment variables are used. 224 229 225 230 4.3 GCC, JDK, Sane, and KDE-multimedia, freetype2, MesaLib and others … … 250 255 4.5 PATCHES 251 256 252 By default, all required patches will be downloaded from the NET. 253 254 If you have previously downloaded the patches, you must edit the 255 scripts to use your local patches. 256 257 Also, be sure that all scripts have the commands to download/apply the 258 required patches. Due to book layout issues, some patches may be missing. 257 Please, make sure that all scripts have the commands to download/apply 258 the required patches. Due to book layout issues, some patches may be 259 missing. 259 260 260 261 4.6 ROOT COMMANDS … … 267 268 sudo bash -c '<commands to be executed as root>' 268 269 which fail if the commands to be executed contain themselves a ' or access 269 a bash variable $XXX. So carefully review them. 270 a bash variable $XXX. So carefully review them. When you want to use 271 environment variables, it is sometimes better to replace simple quotes 272 with double quotes, but beware the construct is even more fragile. 273 Carefully check it... 270 274 271 275 Due to book layout issues, some sudo commands may be missing. … … 276 280 any, please report it to <alfs-discuss@linuxfromscratch.org>. 277 281 278 Presently, there is an error in the book in file279 x/installing/x7proto.xml. You should change the role='required' to280 role='optional' in the optional dependencies, if you plan to build281 X.
Note:
See TracChangeset
for help on using the changeset viewer.