Changeset 50b1fb7


Ignore:
Timestamp:
10/06/2006 07:49:45 PM (18 years ago)
Author:
Manuel Canales Esparcia <manuel@…>
Branches:
2.3, 2.3.x, 2.4, ablfs, ablfs-more, legacy, new_features, trunk
Children:
86d7ef3
Parents:
7b84722
Message:

README updates.

File:
1 edited

Legend:

Unmodified
Added
Removed

  • README

    r7b84722 r50b1fb7  
    55     This collection of scripts, known as jhalfs, strives to create
    66  accurate makefiles from the Linux From Scratch book series XML files.
    7   This software is an evolution of the original "jhalfs-0.2" code.
     7  This software is an evolution of the original "jhalfs-0.2" code developed
     8  by Jeremy Huntwork.
    89
    910     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.
    12  
     11  the book(s) and, therefore, the configuration variables found in menuconfig
     12  interface will have meaning to you.
     13
     14  The list of supported books can be found at
     15  http://wiki.linuxfromscratch.org/alfs/wiki/SupportedBooks
     16
    1317  NOTES::
    1418  *.  The resulting Makefile takes considerable time to run to completion.
    … …  
    36403. INSTALLATION::
    3741
    38      No installation is required. System-wide installation is not allowed
    39   for now.
    40 
    41 4. CONFIGURATION FILES::
    42 
    43      ::NEWS:: There is new configuration method for jhalfs.
     42     No installation is required. System-wide installation is not allowed.
     43
     444. CONFIGURATION::
     45
     46     ::NEWS::
     47         There is a new configuration method for jhalfs.
    4448
    4549     We have installed the familiar menu based configuration tool driven by
    46      by GNU make. see the section RUNNING, for details
     50     GNU make. see the section RUNNING, for details
    4751
    48525. RUNNING::
    4953
    50      ::NEWS:: jhalfs is now launched via GNU make instead of individual symlinks.
     54     ::NEWS::
     55         jhalfs is now launched via GNU make instead of individual symlinks.
     56
    5157     The command <make> will launch a menu based configuration program. You will
    52      recognize the layout from bulding the kernel or uClibc/Busybox. The
    53      underlying menu code was borrowed from BusyBox and slightly modified for 
     58     recognize the layout from building the kernel or uClibc/BusyBox. The
     59     underlying menu code was borrowed from BusyBox and slightly modified for
    5460     our use.
    5561
    56      Help on parameter function is available from the online help.
    57      
    58      Once you have set the parameters you wish and have saved your work the
    59      makefile will proceed to launch the jhalfs script. The script validate and
    60      present you with your selections which you may accept or reject.
    61      
     62     Help on parameter function is available from the online help. Please
     63     make use of that function for additional information not in this file.
     64
     65     Once you have set the parameters you wish and have saved your work the
     66     jhalfs script is launch. The script verify first that the host can run
     67     it and build the xLFS system, then validate the configuration and present
     68     you with your selections which you may accept or reject.
     69
    6270     If you accepted the displayed settings jhalfs will proceed to create the
    63      makefile, optionally download packages.
    64 
    65      NOTE::   
    66      If you run the jhalfs script directly the only funcion you can select is to
    67      display the version number
     71     Makefile, optionally download packages.
     72
     73     ::NEWS::
     74         You must be logged as a normal user with sudo privileges to run
     75         the Makefile.
     76
     77     NOTE::
     78         If you run the jhalfs script directly the only function you can select
     79         is to display the version number running <./jhalfs -v>
    6880
    6981
    70826. LAYOUT::
    7183
    72         /CLFS/config
    73              /master.sh
    74              /xxxx.xsl
    75 
    76         /CLFS2/config
    77               /master.sh
    78               /xxxx.xsl
    79 
    80         /HLFS/config
    81              /master.sh
    82              /xxxx.xsl
    83 
    84         /LFS/config
    85             / master.sh
    86             /xxxx.xsl
    87 
    88         /common/config
    89                /common_functions
     84        /BLFS (see README.BLFS)
     85
     86        /CLFS/master.sh
     87             /clfs.xsl
     88
     89        /CLFS2/master.sh
     90              /clfs2.xsl
     91
     92        /HLFS/master.sh
     93             /hlfs.xsl
     94
     95        /LFS/master.sh
     96            /lfs.xsl
     97
     98        /common/common_functions
    9099               /makefile_functions
    91100               /func_check_versions.sh
    92101               /func_validate_configs.sh
     102               /packages.xsl
     103               /urls.xsl
     104               /create-sbu_du-report.sh
     105               /func_compare.sh
     106               /progress_bar.sh
     107               /blfs-tool-deps/9xx-*
    93108
    94109        /contrib/jhalfs-paco.patch
    95110
    96         /extras/do_copy_files
     111        /extras/do_copy_files
    97112               /do_ica_prep
    98113               /do_ica_work
    … …  
    100115               /filelist
    101116
     117        /optimize/opt_config
     118                 /opt_override
     119                 /optimize_functions
     120                 /opt_config.d/noOpt
     121                              /noSymbols
     122                              /O3pipe
     123                              /O3pipe_march
     124                              /defOpt_fPIC
     125
     126        /menu/*
     127
    102128        README
    103         README.BLFS
    104         README.PACO
    105         TODO
    106 
    107         Config.in
    108         makefile
    109         jhalfs
    110         blfs-tool
     129        README.BLFS
     130        README.HLFS
     131        README.PACO
     132        TODO
     133        LICENSE
     134
     135        Config.in
     136        Makefile
     137        jhalfs
     138        blfs-tool
    111139
    1121407. FAQ::
    … …  
    118146    Q. "It doesn't work!"
    119147    A. Yes it does, try >> make
    120        Remember you must either be 'root' to run this script or have 'sudo' privileges.
     148       Remember you must have 'sudo' privileges.
    121149
    122150    Q. "It still doesn't work"
    123     A. jhalfs was designed to work against the developement versions of the LFS
     151    A. jhalfs was designed to work against the development versions of the LFS
    124152       series of books. Consequently changes in a book(s) sometimes breaks older
    125153       versions of jhalfs. Before you start pulling out your hair download the
    … …  
    134162       The layout below $BUILDDIR is as follows.
    135163       $BUILDDIR/
    136             jhalfs      (makefile,cmd scripts,logs..etc)
    137             sources     (where packages reside)
    138             tools       (temporary bootstrap system)
    139             cross-tools (temporary CLFS only)
    140                 ...
    141             FHS dir structure
    142                 ...
     164            jhalfs      (Makefile, cmd scripts, logs, etc..)
     165            sources     (where packages reside)
     166            tools       (temporary bootstrap system)
     167            cross-tools (temporary CLFS only)
     168                ...
     169            FHS dir structure
     170                ...
     171            blfs_root   (files to use blfs-tool if selected to install it)
    143172
    144173    Q. "What is the function of the SRC_ARCHIVE variable?"
    145     A. When then symlinked master.sh runs it creates a local copy of the
    146        necessary packages in BUILDDIR/sources by downloading the files. If
    147        the variable SRC_ARCHIVE is defined the software will first look in
    148        this location for the file and, if found, will copy it to BUILDDIR/sources.
     174    A. When jhalfs runs and packages download was selected, it creates a local
     175       copy of the necessary packages in BUILDDIR/sources by downloading the
     176       files. If the variable SRC_ARCHIVE is defined the software will first
     177       look in this location for the file and, if found, will copy it to
     178       BUILDDIR/sources.
    149179       If the files are not found in SRC_ARCHIVE _and_ you have write priv to
    150180       the directory any downloaded files will be mirrored there.
    … …  
    152182    Q. "How do I set the SRC_ARCHIVE location?"
    153183    A. The best way to set the value of SRC_ARCHIVE is
     184
    154185       export SRC_ARCHIVE=/wherever/you/store/downloaded/packages
    155                        OR
    156        you can change the setting in common/config.
     186
     187       or you can set the full path in the proper menu entry.
    157188
    158189    Q. "Why have 2 copies of the files?"
    159190    A. The package files must be visible during the chroot phase and this is a
    160191       simple and reliable method of doing so. This method also handles the CLFS
    161        build method where the final build may be done on a separate machine.
    162 
    163     Q. "What is the function of LUSER and LGROUP? There is no cmd line switch"
    164     A. If you are running jhalfs from a low or non-priveledged account you may not
    165        have the priv to create/delete accounts. These variables are adjustable
    166        when invoking make.
     192       boot build method where the final build may be done on a separate machine.
     193
     194    Q. "What is the function of "User account" and "Group account" menu settings?"
     195    A. If you are running jhalfs from a low or non-privileged account you may not
     196       have the priv to create/delete the user needed to build temporally tools.
     197       These settings allow you to use your own user and group name to do that
     198       build steps.
     199
     200       These variables are adjustable also when invoking make:
     201
    167202         $BUILDDIR make LUSER=myaccount LGROUP=mygroup
    168        Then only changes to your account will be the creation of a NEW .bashrc after
    169        saving your original to .bashrc.XXX
    170 
    171     Q. "When I try to build 'xxx' with clfs the makefile fails at the mid-point"
     203
     204       The only changes to your account will be the creation of a NEW .bashrc
     205       after saving your original to .bashrc.XXX
     206
     207    Q. "When I try to build CLFS the Makefile fails at the mid-point"
    172208    A. There could be numerous reasons for the failure but the most likely reason
    173209       is you are doing a cross-build using the 'chroot' method and the target is
    … …  
    178214       'boot' method to create your target code.
    179215       As an extreme example: You can build a sparc target on a x86 platform but
    180        only the temptools phase. You must select the 'boot' method and not the 
     216       only the temptools phase. You must select the 'boot' method and not the
    181217       'chroot.' You must transfer the toolchain to a sparc platform, reboot the
    182218       sparc box and continue the build.
    … …  
    188224  George Boudreau
    189225  Manuel Canales Esparcia
    190   Jeremy Huntwork
Note: See TracChangeset for help on using the changeset viewer.