Changeset 9e627f6
- Timestamp:
- 08/16/2006 08:16:01 PM (18 years ago)
- Branches:
- experimental
- Children:
- 8a8b55a
- Parents:
- c5a6f21
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
README.BLFS
rc5a6f21 r9e627f6 5 5 To automatize packages build from the BLFS book instructions is a huge 6 6 task. The BLFS book isn't linear, some package pages need to use a non 7 defaul layout, there are circular dependencies, several packages can be8 installed on a non default pr ifix, build commands can change based on what7 default layout, there are circular dependencies, several packages can be 8 installed on a non default prefix, build commands can change based on what 9 9 dependencies will be used, etc. 10 10 … … 20 20 2. USAGE:: 21 21 22 Due the complexity of the BLFS book, the scripts/Ma file generation is22 Due the complexity of the BLFS book, the scripts/Makefile generation is 23 23 done in several steps: 24 24 … … 74 74 directory named "HTML" that contains a galeon-based HTML book with all 75 75 dependencies in build order and a "scripts" directory with build scripts 76 that uses sudo for commands that need root privile dges.76 that uses sudo for commands that need root privileges. 77 77 78 78 There is also two other directories that contains files generated while … … 80 80 81 81 Now is the time to review the generated book and scripts, making in the 82 scripts any changes you want to fit your needs. Scripts for ad itional82 scripts any changes you want to fit your needs. Scripts for additional 83 83 packages (i.e., for non-BLFS packages) can be inserted in an easy way. 84 84 … … 94 94 (Text is needed for the installed packages tracking system and like) 95 95 96 3. GENERATED BUILD SCRIPTS ISSUES:: 97 98 In this section known issues with the generated build scripts are 99 discussed. They are due build procedures and BLFS layout particularities 100 than we can't handle. In some cases editing the build scripts is mandatory. 101 You may need also to insert some build script created by you to resolve 102 unhandled dependencies and/or to remove some script and install the 103 affected package by hand. 104 105 3.1 BLFS BOOTSCRIPTS 106 107 For now, bootscripts installation will fail. You will need to edit the 108 scripts for packages that install bootscripts and fix their installation 109 command. That could be fixed in the future, but not sure. 110 111 3.2 PACKAGES CONFIGURATION 112 113 For that packages that have a "Configuration" section, you should to 114 edit it build script to fit the configuration to your needs. 115 116 3.4 PDL and Perl modules. 117 118 The generated scripts for that packages are plainly broken and can't 119 be fixed. You must to replace it by your own ones or install that 120 packages by hand. 121 122 3.4 GCC, JDK, Sane, and KDE-multimedia 123 124 On the pages for that packages, the BLFS book actually have instructions 125 to install two packages. You must to edit the scripts to fix it. We will 126 try to fix some of them, but may not be possible. 127 128 3.5 OTHERS 129 130 May have other issues that we are not aware on them yet. If you find 131 someone, please report it to <alfs-discuss@linuxfromscratch.org>. 132 133 -
blfs
rc5a6f21 r9e627f6 45 45 46 46 see_ya() { 47 echo -e "\n \t${BOLD}Goodbye and thank you for choosing ${L_arrow}jhalfs-X${R_arrow}\n"47 echo -e "\n${L_arrow}${BOLD}jhalfs-X${R_arrow} exit${OFF}\n" 48 48 } 49 49 ##### Simple error TRAPS -
master.sh
rc5a6f21 r9e627f6 15 15 16 16 see_ya() { 17 echo -e "\n \t${BOLD}Goodbye and thank you for choosing ${L_arrow}jhalfs-X${R_arrow}\n"17 echo -e "\n${L_arrow}${BOLD}jhalfs-X${R_arrow} exit${OFF}\n" 18 18 } 19 19 ##### Simple error TRAPS … … 67 67 68 68 case $PROGNAME in 69 clfs2) LFSVRS=development; TREE=branches/clfs-2.0/BOOK ;; 69 clfs2) LFSVRS=development; TREE=branches/clfs-2.0/BOOK ;; 70 70 *) LFSVRS=development; TREE=trunk/BOOK ;; 71 71 esac 72 72 73 73 if [[ ! -z ${BRANCH_ID} ]]; then 74 74 case $BRANCH_ID in … … 99 99 fi 100 100 # These are boolean vars generated from Config.in. 101 # ISSUE: If a boolean parameter is not set <true> that 102 # variable is not defined by the menu app. This can 101 # ISSUE: If a boolean parameter is not set <true> that 102 # variable is not defined by the menu app. This can 103 103 # cause a headache if you are not careful. 104 # The following parameters MUST be created and have a 104 # The following parameters MUST be created and have a 105 105 # default value. 106 106 RUNMAKE=${RUNMAKE:-n} … … 116 116 KEYMAP=${KEYMAP:=none} 117 117 GRSECURITY_HOST=${GRSECURITY_HOST:-n} 118 118 119 119 else 120 120 # … … 355 355 mipsel ) ARCH=mips; TARGET="mipsel-unknown-linux-gnu" ;; 356 356 sparc ) ARCH=sparc; TARGET="sparcv9-unknown-linux-gnu" ;; 357 357 358 358 x86_64-64 ) ARCH=x86_64-64; TARGET="x86_64-unknown-linux-gnu" ;; 359 359 mips64-64 ) ARCH=mips64-64; TARGET="mips-unknown-linux-gnu" ;; … … 361 361 sparc64-64 ) ARCH=sparc64-64; TARGET="sparc64-unknown-linux-gnu" ;; 362 362 alpha ) ARCH=alpha; TARGET="alpha-unknown-linux-gnu" ;; 363 363 364 364 x86_64 ) ARCH=x86_64; TARGET="x86_64-unknown-linux-gnu"; TARGET32="i686-pc-linux-gnu" ;; 365 365 mips64 ) ARCH=mips64; TARGET="mips-unknown-linux-gnu"; TARGET32="mips-unknown-linux-gnu" ;; … … 367 367 sparc64 ) ARCH=sparc64; TARGET="sparc64-unknown-linux-gnu"; TARGET32="sparcv9-unknown-linux-gnu" ;; 368 368 ppc64 ) ARCH=ppc64; TARGET="powerpc64-unknown-linux-gnu"; TARGET32="powerpc-unknown-linux-gnu" ;; 369 369 370 370 * ) echo -e "\n$1 is an unknown or unsupported arch."; exit 1 ;; 371 371 esac
Note:
See TracChangeset
for help on using the changeset viewer.