Changeset 883964a


Ignore:
Timestamp:
Jun 2, 2009, 12:34:13 AM (12 years ago)
Author:
Chris Staub <chris@…>
Branches:
clfs-1.2, clfs-2.1, clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit
Children:
a0833ff
Parents:
94c04f1
Message:

Indentation consistency

Location:
BOOK/boot/x86_64-64
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • BOOK/boot/x86_64-64/bin86.xml

    r94c04f1 r883964a  
    2424
    2525    <para os="a">We are building Bin86 so that we can compile Lilo.
    26       Both <command>as86</command> and <command>ld86</command> need to
    27       run on the host system to assemble x86_64 code. We cannot
    28       compile the whole package like this, but fortunately these two
    29       programs are the only parts we require.</para>
     26    Both <command>as86</command> and <command>ld86</command> need to
     27    run on the host system to assemble x86_64 code. We cannot
     28    compile the whole package like this, but fortunately these two
     29    programs are the only parts we require.</para>
    3030
    3131    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
     
    3838
    3939    <para os="b">The Bin86 package does not contain a <command>configure
    40       </command> script. Natively compile only the necessary parts with:
     40    </command> script. Natively compile only the necessary parts with:
    4141    </para>
    4242
     
    4444make CC=gcc -C ld ld86</userinput></screen>
    4545
    46     <para os="e">Install the assembler and linker where they will be on
    47       the PATH when we build Lilo, using prefixes to show that their
    48       output is not for a native system.</para>
     46    <para os="e">Install the assembler and linker into
     47    <filename class="directory">/cross-tools</filename> so they will be in
     48    the PATH when we build Lilo, using prefixes to show that their
     49    output is not for a native system:</para>
    4950
    5051<screen os="f"><userinput>install -v -m 755 -s as/as86 /cross-tools/bin/${CLFS_TARGET}-as86
  • BOOK/boot/x86_64-64/bootloaders.xml

    r94c04f1 r883964a  
    1212
    1313    <para>On x86 and x86_64 (multilib) architectures, the preferred
    14       bootloader is GRUB. Unfortunately, GRUB doesn't work on x86_64
    15       Pure64 - the stage2 files can be correctly built as 32-bit, but the
    16       <command>grub</command> shell is a 64-bit program, and tries to
    17       execute some of the stage2 routines - this results in a segmentation
    18       fault. Therefore, in the final system we use Lilo as the bootloader.
     14    bootloader is GRUB. Unfortunately, GRUB doesn't work on x86_64
     15    Pure64 - the stage2 files can be correctly built as 32-bit, but the
     16    <command>grub</command> shell is a 64-bit program, and tries to
     17    execute some of the stage2 routines - this results in a segmentation
     18    fault. Therefore, in the final system we use Lilo as the bootloader.
    1919    </para>
    2020
    2121    <para>If you already have a bootloader, such as GRUB, installed on
    22       the system then you should use that to make your new kernel bootable.
    23    </para>
     22    the system then you should use that to make your new kernel bootable.
     23    </para>
    2424
    2525  <note>
    2626    <para>We will now cross-compile Bin86 and Lilo - these instructions
    27       assume you are using an x86_64 machine (e.g. booted fron a Live CD),
    28       either pure64 or multilib. This approach will not work if you are
    29       running the machine as i686, because a 32-bit kernel will not be
    30       able to execute a 64-bit binary to install the bootloader. If that
    31       is the case, you will need to install an i686 bootloader on the
    32       host system.
     27    assume you are using an x86_64 machine (e.g. booted fron a Live CD),
     28    either pure64 or multilib. This approach will not work if you are
     29    running the machine as i686, because a 32-bit kernel will not be
     30    able to execute a 64-bit binary to install the bootloader. If that
     31    is the case, you will need to install an i686 bootloader on the
     32    host system.
    3333    </para>
    3434  </note>
Note: See TracChangeset for help on using the changeset viewer.