- Timestamp:
- 08/24/2006 06:21:41 PM (18 years ago)
- Branches:
- experimental
- Children:
- f694f27
- Parents:
- e0f29c1
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
README
re0f29c1 rc0cf6c8 22 22 uClibc rather than glibc. 23 23 24 2. INSTALLATION:: 24 2. PREREQUISITES:: 25 26 To use this tool you MUST: 27 28 - have experience building {c,h,b}LFS packages 29 - know how to edit and write shell scripts 30 - know how a Makefile works 31 - be able to trace build failures and to find what is causing it 32 (user error, package bug, {c,h,b}LFS command bug, or jhalfs code bug) 33 34 If you don't have the above skill, please don't use this tool. 35 36 37 3. INSTALLATION:: 25 38 No installation is required. System-wide installation is not allowed 26 39 for now. 27 40 28 3. CONFIGURATION FILES::41 4. CONFIGURATION FILES:: 29 42 Each book in the LFS series has its own set of configurable parameters 30 43 as well as the common parameters file. … … 49 62 This will create a new file named configuration but will not launch jhalfs. 50 63 51 4. RUNNING::64 5. RUNNING:: 52 65 The script master.sh cannot be invoked directly but only via the 53 66 supplied symlinks. After editing the config file for the project you wish … … 115 128 116 129 117 5. LAYOUT::130 6. LAYOUT:: 118 131 119 132 /CLFS/config … … 157 170 158 171 159 6. FAQ::172 7. FAQ:: 160 173 Q. "This 'help' file is very sparse" 161 174 A. Yes, it is. This tool, jhalfs, is for those who understand the LFS books
Note:
See TracChangeset
for help on using the changeset viewer.