Changeset 835e40c

Timestamp:

03/08/2023 03:25:48 AM (14 months ago)

Author:

Xi Ruoyao <xry111@…>

Branches:

12.0, 12.0-rc1, 12.1, 12.1-rc1, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/update-glibc

Children:

7160772, a8c261b, d0a9bda4

Parents:

e0fb109

git-author:

Xi Ruoyao <xry111@…> (03/08/2023 03:21:34 AM)

git-committer:

Xi Ruoyao <xry111@…> (03/08/2023 03:25:48 AM)

Message:

Adjustments for /dev/pts

1. Declare UNIX98 PTY requirement in host system requirements and check it in the script. All desktop or server distros should have it now, but let's stop anyone from building on a embedded distro w/o UNIX98 PTY early...
2. Use Expect test suite as a guard against mishandled $LFS/dev/pts.
3. No need to test the basic function of Expect in Binutils anymore because if ($LFS)/dev/pts is not good, the Expect test suite would have failed.

Files:

• chapter02/hostreqs.xml (modified) (2 diffs)
• chapter08/binutils.xml (modified) (1 diff)
• chapter08/expect.xml (modified) (1 diff)

chapter02/hostreqs.xml

@@ -105 +105 @@
       compiling the kernel and configuring the boot loader (assuming the host
       uses GRUB) are located in <xref linkend="chapter-bootable"/>.</para>
+
+      <para>We require the host kernel to support UNIX 98 pseudo terminal
+      (PTY).  It should be enabled on all desktop or server distros shipping
+      Linux &min-kernel; or a newer kernel. If you are building a custom
+      host kernel, ensure <option>CONFIG_UNIX98_PTYS</option> is set to
+      <literal>y</literal> in the kernel configuration.</para>
 
     </listitem>
@@ -231 +237 @@
 ver_kernel &min-kernel;
 
+if mount | grep -q 'devpts on /dev/pts' &amp;&amp; [ -e /dev/ptmx ]
+then echo "OK:    Linux Kernel supports UNIX 98 PTY";
+else echo "ERROR: Linux Kernel does NOT support UNIX 98 PTY"; fi
+
 alias_check() {
    if $1 --version 2>&amp;1 | grep -qi $2

chapter08/binutils.xml

@@ -42 +42 @@
     <title>Installation of Binutils</title>
 
-    <para>Verify that the PTYs are working properly inside the chroot
-    environment by performing a simple test:</para>
-
-<screen><userinput remap="test">expect -c "spawn ls"</userinput></screen>
-
-    <para>This command should output the following:</para>
-
-<screen><computeroutput>spawn ls</computeroutput></screen>
-
-    <para>If, instead, the output includes the message below, then the environment
-    is not set up for proper PTY operation.  This issue needs to be resolved before
-    running the test suites for Binutils and GCC:</para>
-
-<screen><computeroutput>The system has no more ptys.
-Ask your system administrator to create more.</computeroutput></screen>
-<!-- Fixed in binutils-2.39
-    <para>
-      Now make a fix identified upstream that affects building some packages:
-     </para>
-
-<screen><userinput remap="pre">sed -e '/R_386_TLS_LE /i \   || (TYPE) == R_386_TLS_IE \\' \
-    -i ./bfd/elfxx-x86.h</userinput></screen>
--->
     <para>The Binutils documentation recommends building Binutils
     in a dedicated build directory:</para>

chapter08/expect.xml

@@ -83 +83 @@
 <screen><userinput remap="make">make</userinput></screen>
 
+    <important>
+      <para>The test suite for Expect is considered critical.
+      Do not skip it under any circumstances.</para>
+    </important>
+
     <para>To test the results, issue:</para>
 
 <screen><userinput remap="test">make test</userinput></screen>
+
+    <para>If any test fails with the message
+    <quote><computeroutput>The system has no more ptys.  Ask your system
+    administrator to create more</computeroutput></quote>, it indicates
+    you've not mounted the
+    <systemitem class="filesystem">devpts</systemitem> file system
+    correctly.  You need to exit from the chroot environment, read
+    <xref linkend='ch-tools-kernfs'/> again, and ensure the
+    <systemitem class="filesystem">devpts</systemitem> file system (and
+    other virtual kernel file systems) mounted correctly.  Then reenter
+    the chroot environment following <xref linkend='ch-tools-chroot'/>.
+    This issue needs to be resolved before continuing.</para>
 
     <para>Install the package:</para>