Changeset 7785f91


Ignore:
Timestamp:
07/13/2006 08:25:46 PM (18 years ago)
Author:
Manuel Canales Esparcia <manuel@…>
Branches:
1.0, 2.3, 2.3.x, 2.4, ablfs, ablfs-more, legacy, new_features, trunk
Children:
a6655ff
Parents:
f86c600
Message:

Typo fix and trailing spaces clean-up.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • README

    rf86c600 r7785f91  
    3838       If you use the switch -M (automatically run the generated makefile) you
    3939       must be 'root' or you can run the scripts using 'sudo'
    40         i.e.  sudo ./lfs -G -M 
    41        
     40        i.e.  sudo ./lfs -G -M
     41
    4242       If you want to run make manually you can only do so if you are 'root' or
    43        via 'sudo' 
     43       via 'sudo'
    4444        i.e  (from within the jhalfs directory) sudo make
    4545
     
    6161
    6262   >>>> an expanded example
    63    
     63
    6464   export SRC_ARCHIVE=/mnt/SourceFiles
    65    
     65
    6666   ./lfs -D /mnt/partition4 \
    6767         -K ~/jhalfs_configs/linux-2.6.16.19-LFS.config \
    6868         -F ~/jhalfs-configs/fstab-sda3 \
    69          -G -T 0 -M 
     69         -G -T 0 -M
    7070
    7171   explanation:::
    72    
     72
    7373   export SRC_ARCHIVE=/mnt/SourceFiles
    74       # This points to a local archive of existing packages. If the version in 
    75         the archive is incorrect jhalfs will access the net and download the 
     74      # This points to a local archive of existing packages. If the version in
     75        the archive is incorrect jhalfs will access the net and download the
    7676        necessary version and store it here for later use. DO NOT set this to
    7777        $BUILDDIR/sources. If you do not set this variable to a valide directory
    78         ALL package tarballs will be downloaded from the 'net. 
    79 
    80    -D /mnt/partition4 
     78        ALL package tarballs will be downloaded from the 'net.
     79
     80   -D /mnt/partition4
    8181      # where everything takes place.  ..NOTE it must already exist and be mounted
    82      
     82
    8383   -K ~/jhalfs_configs/linux-2.6.16.19-LFS.config
    84       # If you want to automatically build a the kernel you MUST supply a valid 
     84      # If you want to automatically build a the kernel you MUST supply a valid
    8585        kernel configuration file. The file you supply will be copied and renamed.
    8686
    87    -F ~/jhalfs-configs/fstab-sda3 
    88       # If you have a fstab file you wish to use it will be copied and renamed 
    89      
    90    -G   # Retrieve the package files. You MUST enable this flag at least once if you 
     87   -F ~/jhalfs-configs/fstab-sda3
     88      # If you have a fstab file you wish to use it will be copied and renamed
     89
     90   -G   # Retrieve the package files. You MUST enable this flag at least once if you
    9191          wish to do a build or whenever you update the book.
    92    
     92
    9393   -T 0 # don't run any testsuites
    94    
     94
    9595   -M   # automatically run make against Makefile once jhalfs finishes its work.
    9696
    97    
     97
    98985. LAYOUT::
    9999
     
    136136    Q. "It doesn't work!"
    137137    A. Yes it does, try ./lfs --help
    138    
     138
    139139    Q. "It still doesn't work"
    140140    A. jhalfs was designed to work against the developement versions of the LFS
    141141       series of books. Consequently changes in a book(s) sometimes breaks older
    142142       versions of jhalfs. Before you start pulling out your hair download the
    143        latest version of jhalfs is see it that solves your problem.
     143       latest version of jhalfs to see if that solves your problem.
    144144
    145145    Q. "How do I specify the build location?"
     
    184184       method a test is performed at the end of the temptools phase. If the test
    185185       succeeds the build continues inside a chroot jail. However if the test fails
    186        it means the host and target are not compatible an you should use the 
    187        'boot' method to create your target code.       
    188        As an extreme example: You can build a sparc target on a x86 platform but 
     186       it means the host and target are not compatible an you should use the
     187       'boot' method to create your target code.
     188       As an extreme example: You can build a sparc target on a x86 platform but
    189189       only the temptools phase. You must run ./clfs using the 'boot' method and
    190        not the 'chroot.' You must transfer the toolchain to a sparc platform, reboot 
     190       not the 'chroot.' You must transfer the toolchain to a sparc platform, reboot
    191191       the sparc box and continue the build.
    192        Of all the LFS series of books the Cross-LFS requires the greatest 
     192       Of all the LFS series of books the Cross-LFS requires the greatest
    193193       understanding of host/target hardware combination. Please read the book
    194194       carefully and don't skip the easy parts (there are none..)
    195        
     195
    196196
    197197
Note: See TracChangeset for help on using the changeset viewer.