Changeset f2ad938 in clfs-embedded


Ignore:
Timestamp:
Oct 14, 2013, 8:57:24 AM (9 years ago)
Author:
Andrew Bradford <andrew@…>
Branches:
master
Children:
a94093c
Parents:
cff561f
git-author:
Andrew Bradford <andrew@…> (10/10/2013 08:03:26 AM)
git-committer:
Andrew Bradford <andrew@…> (10/14/2013 08:57:24 AM)
Message:

materials: Move sources dir create with ${CLFS}

So that ${CLFS} and ${CLFS}/sources are created together.

Location:
BOOK/materials/common
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • BOOK/materials/common/creatingbuilddir.xml

    rcff561f rf2ad938  
    99  <?dbhtml filename="creatingbuilddir.html"?>
    1010
    11   <title>Creating a Build Directory</title>
     11  <title>Creating Build and Sources Directories</title>
    1212
    1313  <para> Create a directory for the CLFS build (the exact location is up to
     
    2525<screen><userinput>chmod 777 ${CLFS}</userinput></screen>
    2626
    27   <para>Now that there is an established place to work, it is time to
    28   download the packages.</para>
     27  <para>Downloaded packages and patches will need to be stored somewhere
     28  that is conveniently available throughout the entire build. A working
     29  directory is also required to unpack the sources and build them.
     30  <filename class="directory">${CLFS}/sources</filename> can be used both
     31  as the place to store the tarballs and patches and as a working
     32  directory.</para>
     33
     34  <para>Create a directory to store the sources:</para>
     35
     36<screen><userinput>mkdir -v ${CLFS}/sources</userinput></screen>
    2937
    3038</sect1>
  • BOOK/materials/common/introduction.xml

    rcff561f rf2ad938  
    1111  <title>Introduction</title>
    1212
    13   <para>This chapter includes a list of packages that need to be downloaded
    14   for building a basic Linux system. The listed version numbers correspond
    15   to versions of the software that are known to work, and this book is based
    16   on their use. We highly recommend not using newer versions because the
    17   build commands for one version may not work with a newer version. The
    18   newest package versions may also have problems that require work-arounds.
    19   These work-arounds will be developed and stabilized in the development
    20   version of the book.</para>
     13  <para>This chapter creates a directory where the cross compiler toolchain wil
     14  be built and a directory where sources are kept.  It includes a list of
     15  packages that need to be downloaded for building a basic Linux
     16  system.</para>
     17
     18  <para>The listed version numbers correspond to versions of the software that
     19  are known to work, and this book is based on their use. We highly recommend
     20  not using newer or older versions because the build commands for one version may not
     21  work with another version.</para>
    2122
    2223  <para>Download locations may not always be accessible. If a download
     
    2526  most packages.</para>
    2627
    27   <para>Downloaded packages and patches will need to be stored somewhere
    28   that is conveniently available throughout the entire build. A working
    29   directory is also required to unpack the sources and build them.
    30   <filename class="directory">${CLFS}/sources</filename> can be used both
    31   as the place to store the tarballs and patches and as a working
    32   directory. By using this directory, the required elements will be
    33   located on the CLFS partition and will be available during all stages
    34   of the building process.</para>
    35 
    36   <para>To create this directory, execute, as user <systemitem
    37   class="username">root</systemitem>, the following command before
    38   starting the download session:</para>
    39 
    40 <screen><userinput>mkdir -v ${CLFS}/sources</userinput></screen>
    41 
    42   <para>Make this directory writable and sticky. When a directory is
    43   marked <quote>sticky</quote>, that means that even if multiple users have
    44   write permission on that directory, any file within that directory can only be
    45   deleted or modified by its owner. The following command will enable the
    46   write and sticky modes:</para>
    47 
    48 <screen><userinput>chmod -v a+wt ${CLFS}/sources</userinput></screen>
    49 
    5028</sect1>
Note: See TracChangeset for help on using the changeset viewer.