Ignore:
Timestamp:
03/21/2020 11:02:56 AM (4 years ago)
Author:
Pierre Labastie <pieere@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
baac59c
Parents:
bdfc854
Message:

Format the x/installing chapter

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@22865 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:
1 edited

Legend:

Unmodified
Added
Removed

  • x/installing/xorg7.xml

    rbdfc854 r71df408  
    2121
    2222
    23   <para><application>Xorg</application> is a freely redistributable,
    24   open-source implementation of the <application>X</application> Window
    25   System. This system provides a client/server interface between display
    26   hardware (the mouse, keyboard, and video displays) and the desktop
    27   environment, while also providing both the windowing infrastructure and a
    28   standardized application interface (API).</para>
     23  <para>
     24    <application>Xorg</application> is a freely redistributable,
     25    open-source implementation of the <application>X</application> Window
     26    System. This system provides a client/server interface between display
     27    hardware (the mouse, keyboard, and video displays) and the desktop
     28    environment, while also providing both the windowing infrastructure and a
     29    standardized application interface (API).
     30  </para>
    2931
    3032  <para condition="html" role="usernotes">User Notes:
    … …  
    3436  Instructions</bridgehead>
    3537
    36   <para>Xorg-7.0 introduced a completely auto-tooled, modular build system.
    37   With the new modular build system, it is no longer possible to download
    38   the entire package in a single file. In fact, there will be well over 100
    39   packages that need to be fetched from the download location. To assist
    40   with such a large task, installing <xref linkend="wget"/> is strongly
    41   recommended for downloading the needed files.  A complete
    42   <application>wget</application> file list is provided for each page
    43   that includes multiple packages.</para>
    44 
    45   <para>Given the number of packages available, deciding which packages you
    46   need to install for your particular setup may seem a bit overwhelming at
    47   first.  Take a look at
    48   <ulink url="http://wiki.x.org/wiki/ModuleDescriptions">this page</ulink>
    49   and
    50   <ulink url="http://lists.x.org/archives/xorg-modular/2005-November/000801.html">this thread</ulink>
    51   to get an idea of what you will need.  If you are unsure, you should
    52   install all packages at the cost of extra disk space.</para>
     38  <para>
     39    Xorg-7.0 introduced a completely auto-tooled, modular build system.
     40    With the new modular build system, it is no longer possible to download
     41    the entire package in a single file. In fact, there will be well over 100
     42    packages that need to be fetched from the download location. To assist
     43    with such a large task, installing <xref linkend="wget"/> is strongly
     44    recommended for downloading the needed files.  A complete
     45    <application>wget</application> file list is provided for each page
     46    that includes multiple packages.
     47  </para>
     48
     49  <para>
     50    Given the number of packages available, deciding which packages you
     51    need to install for your particular setup may seem a bit overwhelming at
     52    first.  Take a look at <ulink url=
     53    "http://wiki.x.org/wiki/ModuleDescriptions">this page</ulink>
     54    and <ulink url=
     55    "http://lists.x.org/archives/xorg-modular/2005-November/000801.html">
     56    this thread</ulink>
     57    to get an idea of what you will need.  If you are unsure, you should
     58    install all packages at the cost of extra disk space.
     59  </para>
    5360
    5461  <note>
    55     <para>Even if you intend to download only the necessary packages, you
    56     should download the wget file lists.  The list of files are ordered by
    57     dependency, and the package versions listed in the files are known to
    58     work well with each other. Further, the wget file lists contain comments
    59     for specific packages that are deprecated or are not recommended to
    60     install. Newer packages are likely intended for the
    61     next release of <application>Xorg</application> and have already proved
    62     to be incompatible with current versions of software installed in BLFS.
    63     The installed size of <application>Xorg</application> can be reduced
    64     considerably by installing only the packages that you will need and use,
    65     however, the BLFS book cannot account for all dependencies and build
    66     options for the individual <application>Xorg</application> packages.
    67     The instructions assume that all packages have been built.  A
    68     <ulink url="&blfs-wiki;/Xorg7">wiki</ulink>
    69     page containing dependency information is under development.  You are
    70     encouraged to add to these pages if you discover additional information
    71     that may be helpful to other users who selectively install individual
    72     packages.</para>
     62    <para>
     63      Even if you intend to download only the necessary packages, you
     64      should download the wget file lists.  The list of files are ordered by
     65      dependency, and the package versions listed in the files are known to
     66      work well with each other. Further, the wget file lists contain comments
     67      for specific packages that are deprecated or are not recommended to
     68      install. Newer packages are likely intended for the
     69      next release of <application>Xorg</application> and have already proved
     70      to be incompatible with current versions of software installed in BLFS.
     71      The installed size of <application>Xorg</application> can be reduced
     72      considerably by installing only the packages that you will need and use,
     73      however, the BLFS book cannot account for all dependencies and build
     74      options for the individual <application>Xorg</application> packages.
     75      The instructions assume that all packages have been built.  A
     76      <ulink url="&blfs-wiki;/Xorg7">wiki</ulink>
     77      page containing dependency information is under development.  You are
     78      encouraged to add to these pages if you discover additional information
     79      that may be helpful to other users who selectively install individual
     80      packages.
     81    </para>
    7382  </note>
    7483
    75   <para>Additionally, because of the large number of repetitive commands,
    76   you are encouraged to partially automate the build. Instructions have been
    77   given that utilize the <xref linkend="sudo"/> package. It is recommended that
    78   you use the <parameter>:NOPASSWD</parameter> configuration option for the
    79   user that will be building the xorg packages.</para>
     84  <para>
     85    Additionally, because of the large number of repetitive commands,
     86    you are encouraged to partially automate the build. Instructions have been
     87    given that utilize the <xref linkend="sudo"/> package. It is recommended
     88    that you use the <parameter>:NOPASSWD</parameter> configuration option
     89    for the user that will be building the xorg packages.
     90  </para>
    8091
    8192  <sect2 id="xorg-env" xreflabel="Xorg build environment">
    8293    <title>Setting up the Xorg Build Environment</title>
    8394
    84     <note><para>The following instructions assume that the shell
    85     startup files have been set up as described in
    86     <xref linkend="postlfs-config-profile" />.
    87     </para></note>
    88 
    89     <para>First, you'll need to create a working directory:</para>
     95    <note>
     96      <para>
     97        The following instructions assume that the shell
     98        startup files have been set up as described in
     99        <xref linkend="postlfs-config-profile" />.
     100      </para>
     101    </note>
     102
     103    <para>
     104      First, you'll need to create a working directory:
     105    </para>
    90106
    91107<screen><userinput>mkdir xc &amp;&amp;
    92108cd xc</userinput></screen>
    93109
    94     <para>As with previous releases of the X Window System, it may be
    95     desirable to install <application>Xorg</application> into an alternate
    96     prefix.  This is no longer common practice among Linux distributions.
    97     The common installation prefix for <application>Xorg</application> on
    98     Linux is <filename class="directory">/usr</filename>.  There is no
    99     standard alternate prefix, nor is there any exception in the current
    100     revision of the Filesystem Hierarchy Standard for Release 7 of the X
    101     Window System.  Alan Coopersmith of Sun Microsystems, once
    102     stated "At Sun, we were using
    103     <filename class="directory">/usr/X11</filename> and plan to stick with
    104     it."  Only the <filename class="directory">/opt/*</filename> prefix or
    105     the <filename class="directory">/usr</filename> prefix adhere to the
    106     current FHS guidelines.</para>
    107 
    108     <para>Choose your installation prefix, and set the
    109     <envar>XORG_PREFIX</envar> variable with the following
    110     command:</para>
     110    <para>
     111      As with previous releases of the X Window System, it may be
     112      desirable to install <application>Xorg</application> into an alternate
     113      prefix.  This is no longer common practice among Linux distributions.
     114      The common installation prefix for <application>Xorg</application> on
     115      Linux is <filename class="directory">/usr</filename>.  There is no
     116      standard alternate prefix, nor is there any exception in the current
     117      revision of the Filesystem Hierarchy Standard for Release 7 of the X
     118      Window System.  Alan Coopersmith of Sun Microsystems, once
     119      stated "At Sun, we were using
     120      <filename class="directory">/usr/X11</filename> and plan to stick with
     121      it."  Only the <filename class="directory">/opt/*</filename> prefix or
     122      the <filename class="directory">/usr</filename> prefix adhere to the
     123      current FHS guidelines.
     124    </para>
     125
     126    <para>
     127      Choose your installation prefix, and set the <envar>XORG_PREFIX</envar>
     128      variable with the following command:
     129    </para>
    111130
    112131<screen><userinput>export XORG_PREFIX="<replaceable>&lt;PREFIX&gt;</replaceable>"</userinput></screen>
    113132
    114     <para>Throughout these instructions, you will use the following
    115     <command>configure</command> switches for all of the packages.  Create the
    116     <envar>XORG_CONFIG</envar> variable to use for this parameter
    117     substitution:</para>
     133    <para>
     134      Throughout these instructions, you will use the following
     135      <command>configure</command> switches for all of the packages. Create the
     136      <envar>XORG_CONFIG</envar> variable to use for this parameter
     137      substitution:
     138    </para>
    118139
    119140<screen><userinput>export XORG_CONFIG="--prefix=$XORG_PREFIX --sysconfdir=/etc \
    120141    --localstatedir=/var --disable-static"</userinput></screen>
    121142
    122     <para>Create an <filename>/etc/profile.d/xorg.sh</filename> configuration
    123     file containing these variables as the
    124     <systemitem class="username">root</systemitem> user:</para>
     143    <para>
     144      Create an <filename>/etc/profile.d/xorg.sh</filename> configuration
     145      file containing these variables as the
     146      <systemitem class="username">root</systemitem> user:
     147    </para>
    125148
    126149<screen role="root"><userinput>cat &gt; /etc/profile.d/xorg.sh &lt;&lt; EOF
    … …  
    131154chmod 644 /etc/profile.d/xorg.sh</userinput></screen>
    132155
    133     <note><para>There is some confustion about the above 'here' document.
    134     The backslash in front of the dollar sign is correct.  Bash
    135     will remove it when creating /etc/profile.d/xorg.sh.  However, if
    136     you are creating the file with an editor, a copy and paste operation
    137     will not remove the baskslash.  It must then be removed manually.
    138     </para></note>
     156    <note>
     157      <para>
     158        There is some confustion about the above 'here' document.
     159        The backslash in front of the dollar sign is correct.  Bash
     160        will remove it when creating /etc/profile.d/xorg.sh.  However, if
     161        you are creating the file with an editor, a copy and paste operation
     162        will not remove the baskslash.  It must then be removed manually.
     163      </para>
     164    </note>
    139165
    140166    <para>
    … …  
    151177EOF</userinput></screen>
    152178
    153     <note><para>If you've decided to use the standard <filename
    154     class="directory">/usr</filename> prefix, you can omit the remainder of
    155     this page and continue at <xref linkend='util-macros'/>.</para></note>
    156 
    157     <para>If you've decided to <emphasis>not</emphasis> use the standard
    158     prefix, be sure to add <filename
    159     class="directory">$XORG_PREFIX/bin</filename> to your <envar>PATH</envar>
    160     environment variable, and <filename class="directory">
    161     $XORG_PREFIX/lib/pkgconfig</filename> and <filename class="directory">
    162     $XORG_PREFIX/share/pkgconfig</filename> to your
    163     <envar>PKG_CONFIG_PATH</envar> variable. It is also helpful to specify
    164     additional search paths for <command>gcc</command> and an include directory
    165     for the <command>aclocal</command> program.  Issue the following commands
    166     as the <systemitem class="username">root</systemitem> user:</para>
     179    <note>
     180      <para>
     181        If you've decided to use the standard <filename
     182        class="directory">/usr</filename> prefix, you can omit the remainder of
     183        this page and continue at <xref linkend='util-macros'/>.
     184      </para>
     185    </note>
     186
     187    <para>
     188      If you've decided to <emphasis>not</emphasis> use the standard
     189      prefix, be sure to add <filename
     190      class="directory">$XORG_PREFIX/bin</filename> to your <envar>PATH</envar>
     191      environment variable, and <filename class="directory">
     192      $XORG_PREFIX/lib/pkgconfig</filename> and <filename class="directory">
     193      $XORG_PREFIX/share/pkgconfig</filename> to your
     194      <envar>PKG_CONFIG_PATH</envar> variable. It is also helpful to specify
     195      additional search paths for <command>gcc</command> and an include
     196      directory for the <command>aclocal</command> program.  Issue the
     197      following commands as the <systemitem class="username">root</systemitem>
     198      user:
     199    </para>
    167200
    168201<screen role="root"><userinput>cat &gt;&gt; /etc/profile.d/xorg.sh &lt;&lt; "EOF"
    … …  
    181214EOF</userinput></screen>
    182215
    183     <para>The script above needs to be activated.  Normally it will be
    184     automatic at login, but to activate it now, as a regular user, run:</para>
     216    <para>
     217      The script above needs to be activated.  Normally it will be
     218      automatic at login, but to activate it now, as a regular user, run:
     219    </para>
    185220
    186221<screen><userinput>source /etc/profile.d/xorg.sh</userinput></screen>
    187222
    188     <para>You should also add
    189     <filename class="directory"> $XORG_PREFIX/lib</filename> to the
    190     <filename>/etc/ld.so.conf</filename> file. Again, as the
    191     <systemitem class="username">root</systemitem> user, issue the following
    192     command:</para>
     223    <para>
     224      You should also add
     225      <filename class="directory"> $XORG_PREFIX/lib</filename> to the
     226      <filename>/etc/ld.so.conf</filename> file. Again, as the
     227      <systemitem class="username">root</systemitem> user, issue the following
     228      command:
     229    </para>
    193230
    194231<screen role="root"><userinput>echo "$XORG_PREFIX/lib" >> /etc/ld.so.conf</userinput></screen>
    195232
    196     <para>You should also modify
    197     <filename>/etc/man_db.conf</filename>, adding appropriate
    198     MANDATORY_MANPATH, MANPATH_MAP, and MANDB_MAP entries following the
    199     examples for <filename class="directory">/usr/X11R6</filename>. Issue the
    200     following command as the <systemitem class="username">root</systemitem>
    201     user:</para>
     233    <para>
     234      You should also modify
     235      <filename>/etc/man_db.conf</filename>, adding appropriate
     236      MANDATORY_MANPATH, MANPATH_MAP, and MANDB_MAP entries following the
     237      examples for <filename class="directory">/usr/X11R6</filename>. Issue the
     238      following command as the <systemitem class="username">root</systemitem>
     239      user:
     240    </para>
    202241
    203242<screen role="root"><userinput>sed "s@<replaceable>/usr/X11R6</replaceable>@$XORG_PREFIX@g" -i /etc/man_db.conf</userinput></screen>
    204243
    205     <para>Some applications look for shared files in <filename
    206     class="directory">/usr/share/X11</filename>.  Create a symbolic link to the
    207     proper location as the <systemitem class="username">root</systemitem>
    208     user:</para>
     244    <para>
     245      Some applications look for shared files in <filename
     246      class="directory">/usr/share/X11</filename>.  Create a symbolic link to
     247      the proper location as the <systemitem class="username">root</systemitem>
     248      user:
     249    </para>
    209250
    210251<screen role="root"><userinput>ln -svf $XORG_PREFIX/share/X11 /usr/share/X11</userinput></screen>
    211252
    212     <para>If building KDE, some cmake files look for Xorg in places other than
    213     $XORG_PREFIX.  Allow cmake to find Xorg with:</para>
     253    <para>
     254      If building KDE, some cmake files look for Xorg in places other than
     255      $XORG_PREFIX.  Allow cmake to find Xorg with:
     256    </para>
    214257
    215258<screen role="root"><userinput>ln -svf $XORG_PREFIX /usr/X11R6</userinput></screen>
    216259<!--
    217     <para>Finally, if building on x86_64, you will need to create the
    218     <filename class="directory">$XORG_PREFIX/lib</filename> directory and the
    219     <filename>$XORG_PREFIX/lib64</filename> symlink. Again, as the
    220     <systemitem class="username">root</systemitem> user, issue the following
    221     commands:</para>
     260    <para>
     261      Finally, if building on x86_64, you will need to create the
     262      <filename class="directory">$XORG_PREFIX/lib</filename> directory and the
     263      <filename>$XORG_PREFIX/lib64</filename> symlink. Again, as the
     264      <systemitem class="username">root</systemitem> user, issue the following
     265      commands:
     266    </para>
    222267
    223268<screen role="root"><userinput>install -v -m755 -d $XORG_PREFIX &amp;&amp;
Note: See TracChangeset for help on using the changeset viewer.