Changeset a6d199da


Ignore:
Timestamp:
08/17/2022 10:04:03 AM (7 weeks ago)
Author:
Pierre Labastie <pierre.labastie@…>
Branches:
11.2, trunk, xry111/soup3
Children:
66f6b74
Parents:
8859e30
Message:

Add glibc-2.36 patch for systemd in BLFS

File:
1 edited

Legend:

Unmodified
Added
Removed
  • general/sysutils/systemd.xml

    r8859e30 ra6d199da  
    7878    </itemizedlist>
    7979
    80 <!--  Keep here in case a patch will be needed.
     80<!--  Keep here in case a patch will be needed.-->
    8181    <bridgehead renderas="sect3">Additional Downloads</bridgehead>
    8282    <itemizedlist spacing="compact">
     
    8484        <para>
    8585         Required patch:
    86          <ulink url="&patch-root;/systemd-..."/>
     86         <ulink url="&patch-root;/systemd-&systemd-version;-glibc_2.36_fix-1.patch"/>
    8787        </para>
    8888      </listitem>
    8989    </itemizedlist>
    90 -->
    9190
    9291    <bridgehead renderas="sect3">systemd Dependencies</bridgehead>
     
    153152
    154153    <para>
     154      First, fix building <application>systemd</application> with glibc-2.36:
     155    </para>
     156
     157<screen><userinput>patch -Np1 -i ../systemd-&systemd-version;-glibc_2.36_fix-1.patch</userinput></screen>
     158
     159    <para>
    155160      Remove two unneeded groups,
    156161      <systemitem class="groupname">render</systemitem> and
     
    203208    </para>
    204209
    205 <!--
    206     <warning>
    207       <para>
    208         Installing the package will overwrite all files installed by
    209         <application>systemd</application> in LFS. It is critical that
    210         nothing uses either <application>systemd</application> or
    211         <application>Udev</application> libraries during the installation.
    212         The best way to ensure that these libraries are not being used is to
    213         run the installation in rescue mode. To switch to rescue mode,
    214         run the following command as the
    215         <systemitem class="username">root</systemitem> user (from a TTY):
    216       </para>
    217 
    218 <screen role="root"><userinput>systemctl isolate rescue.target</userinput></screen>
    219     </warning>
    220     Nobody has reported problems with this in years. Let's comment it. -->
    221 
    222210   <para>
    223211     Now, as the <systemitem class="username">root</systemitem> user:
     
    226214<screen role="root"><userinput>ninja install</userinput></screen>
    227215
    228 <!-- Included in the patch
    229     <para>
    230       Fix a problem in a systemd unit that can cause extra delays when
    231       changing TTYs:
    232     </para>
    233 
    234 <screen role="root"><userinput>sed -i 's/idle/simple/' /usr/lib/systemd/system/getty@.service</userinput></screen>
    235 -->
    236   <!-- No longer needed as of systemd-244.
    237     <para>
    238       Remove a configuration file that causes some problems with PID files:
    239     </para>
    240 
    241 <screen role="root"><userinput>rm -fv /etc/sysctl.d/50-pid-max.conf</userinput></screen>
    242   -->
    243216  </sect2>
    244217
    245218  <sect2 role="commands">
    246219    <title>Command Explanations</title>
    247 
    248 <!-- Not needed with the patch
    249     <para>
    250       <parameter>-Dc_args=-Wno-format-overflow</parameter>: Prevents an error
    251       when building with <application>GCC 10</application>. The default is
    252       <option>-Werror=format-overflow</option>,
    253       which generates false positives. This switch may be used with previous
    254       versions of GCC too.
    255     </para>
    256 -->
    257220
    258221    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
     
    352315# End /etc/pam.d/systemd-user</literal>
    353316EOF</userinput></screen>
    354 
    355 <!--
    356     <para>
    357       At this point, you should reload the systemd daemon, and reenter
    358       multi-user mode with the following commands (as the
    359       <systemitem class="username">root</systemitem> user).  If a desktop
    360       manager is installed and you wish to reenter the graphical mode,
    361       replace <userinput>multi-user.target</userinput> with
    362       <userinput>graphical.target</userinput>:
    363     </para>
    364 
    365 <screen role="root"><userinput>systemctl daemon-reexec
    366 systemctl start multi-user.target</userinput></screen>-->
    367317
    368318    <warning>
Note: See TracChangeset for help on using the changeset viewer.