Changeset 25cd02b
- Timestamp:
- 03/10/2023 01:51:42 AM (14 months ago)
- 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:
- 34f1344
- Parents:
- 6e4dfa7 (diff), de67916 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the(diff)
links above to see all the changes relative to each parent. - Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter02/hostreqs.xml
r6e4dfa7 r25cd02b 105 105 compiling the kernel and configuring the boot loader (assuming the host 106 106 uses GRUB) are located in <xref linkend="chapter-bootable"/>.</para> 107 108 <para>We require the host kernel to support UNIX 98 pseudo terminal 109 (PTY). It should be enabled on all desktop or server distros shipping 110 Linux &min-kernel; or a newer kernel. If you are building a custom 111 host kernel, ensure <option>CONFIG_UNIX98_PTYS</option> is set to 112 <literal>y</literal> in the kernel configuration.</para> 107 113 108 114 </listitem> … … 231 237 ver_kernel &min-kernel; 232 238 239 if mount | grep -q 'devpts on /dev/pts' && [ -e /dev/ptmx ] 240 then echo "OK: Linux Kernel supports UNIX 98 PTY"; 241 else echo "ERROR: Linux Kernel does NOT support UNIX 98 PTY"; fi 242 233 243 alias_check() { 234 244 if $1 --version 2>&1 | grep -qi $2 -
chapter08/binutils.xml
r6e4dfa7 r25cd02b 42 42 <title>Installation of Binutils</title> 43 43 44 <para>Verify that the PTYs are working properly inside the chroot45 environment by performing a simple test:</para>46 47 <screen><userinput remap="test">expect -c "spawn ls"</userinput></screen>48 49 <para>This command should output the following:</para>50 51 <screen><computeroutput>spawn ls</computeroutput></screen>52 53 <para>If, instead, the output includes the message below, then the environment54 is not set up for proper PTY operation. This issue needs to be resolved before55 running the test suites for Binutils and GCC:</para>56 57 <screen><computeroutput>The system has no more ptys.58 Ask your system administrator to create more.</computeroutput></screen>59 <!-- Fixed in binutils-2.3960 <para>61 Now make a fix identified upstream that affects building some packages:62 </para>63 64 <screen><userinput remap="pre">sed -e '/R_386_TLS_LE /i \ || (TYPE) == R_386_TLS_IE \\' \65 -i ./bfd/elfxx-x86.h</userinput></screen>66 -->67 44 <para>The Binutils documentation recommends building Binutils 68 45 in a dedicated build directory:</para> -
chapter08/expect.xml
r6e4dfa7 r25cd02b 83 83 <screen><userinput remap="make">make</userinput></screen> 84 84 85 <important> 86 <para>The test suite for Expect is considered critical. 87 Do not skip it under any circumstances.</para> 88 </important> 89 85 90 <para>To test the results, issue:</para> 86 91 87 92 <screen><userinput remap="test">make test</userinput></screen> 93 94 <para>If any test fails with the message 95 <quote><computeroutput>The system has no more ptys. Ask your system 96 administrator to create more</computeroutput></quote>, it indicates 97 you've not mounted the 98 <systemitem class="filesystem">devpts</systemitem> file system 99 correctly. You need to exit from the chroot environment, read 100 <xref linkend='ch-tools-kernfs'/> again, and ensure the 101 <systemitem class="filesystem">devpts</systemitem> file system (and 102 other virtual kernel file systems) mounted correctly. Then reenter 103 the chroot environment following <xref linkend='ch-tools-chroot'/>. 104 This issue needs to be resolved before continuing.</para> 88 105 89 106 <para>Install the package:</para> -
chapter10/kernel.xml
r6e4dfa7 r25cd02b 97 97 <ulink url="http://www.kroah.com/lkn/"/> </para> 98 98 99 <caution> 100 <para>A good starting place for setting up the kernel configuration is to 101 run <command>make localmodconfig</command>. If the host kernel version 102 is not too different from the version of the kernel you are building, 103 this will set the base configuration to a good state similar to what 104 the host uses. Another possibility is to use <command>make 105 localyesconfig</command>, which does the same except everything is built 106 into the kernel.</para> 107 108 <para>Do not disable any option enabled by <command>make 109 localmodconfig</command> unless the following notes explicitly make it 110 disabled or you really know what you are doing.</para> 111 </caution> 112 99 113 <note> 100 <para>A good starting place for setting up the kernel configuration is to 101 run <command>make defconfig</command>. This will set the base 102 configuration to a good state that takes your current system architecture 103 into account.</para> 104 114 <para>Another possibility is to run <command>make defconfig</command>, 115 which creates a more generic configuration for your architecture. You 116 may then have to disable drivers for hardware you do not have if 117 you want to reduce the kernel size.</para> 118 </note> 119 120 <note> 105 121 <para>Be sure to enable/disable/set the following features or the system might 106 122 not work correctly or boot at all:</para> … … 112 128 [ ] Compile the kernel with warnings as errors [CONFIG_WERROR] 113 129 < > Enable kernel headers through /sys/kernel/kheaders.tar.xz [CONFIG_IKHEADERS] 130 [ ] Configure standard kernel features (expert users) [CONFIG_EXPERT] 114 131 General architecture-dependent options ---> 115 132 [*] Stack Protector buffer overflow detection [CONFIG_STACKPROTECTOR] … … 138 155 [*] Memory controller [CONFIG_MEMCG] 139 156 [ ] Enable deprecated sysfs features to support old userspace tools [CONFIG_SYSFS_DEPRECATED] 140 [*] Configure standard kernel features (expert users) [CONFIG_EXPERT] ---> 141 [*] open by fhandle syscalls [CONFIG_FHANDLE] 157 [ ] Configure standard kernel features (expert users) [CONFIG_EXPERT] 142 158 General architecture-dependent options ---> 143 159 [*] Enable seccomp to safely compute untrusted bytecode [CONFIG_SECCOMP] … … 238 254 239 255 <varlistentry> 256 <term> 257 <parameter> 258 Configure standard kernel features (expert users) 259 </parameter> 260 </term> 261 <listitem> 262 <para>This will make some options show up in the configuration 263 interface but changing those options may be dangerous. Do not use 264 this unless you know what you are doing.</para> 265 </listitem> 266 </varlistentry> 267 268 <varlistentry> 240 269 <term><parameter>Strong Stack Protector</parameter></term> 241 270 <listitem> … … 294 323 processors in x2APIC mode. x2APIC may be enabled by firmware on 295 324 64-bit x86 systems, and a kernel without this option enabled will 296 panic on boot if x2APIC is enabled by firmware. This option has325 panic on boot if x2APIC is enabled by firmware. This option 297 326 has no effect, but also does no harm if x2APIC is disabled by the 298 327 firmware.</para>
Note:
See TracChangeset
for help on using the changeset viewer.