Changes between Version 5 and Version 6 of cross-chap5

Timestamp:

05/05/2020 12:23:06 PM (5 years ago)

Author:

thomas

Comment:

--

cross-chap5

@@ -61 +61 @@
 === Phenomenon on ArchLinux
 
- Issue:: Moody, 04.05.2020:
+==== glibc in ch6 failes with "bison: m4 subprocess failed" (Moody, 04.05.2020)
+  (solved/workaround)
 
   While it has been reported (in IRC) that others have build CC5 successfully on Arch, here is what happens when compiling `glibc` in Chap6 after installing man-pages:
@@ -92 +93 @@
 }}}
 
-  Also, when in chroot, tar reports **tar: write error** just like this one discussed ten years ago:  https://www.mail-archive.com/lfs-support@linuxfromscratch.org/msg13073.html
-
   This all does not happen when running the build on a LFS-SVN host.
 
- Solution::
-  <currently none>
  Discussion::
   There are only warnings, then the error is about a missing file when running the m4 subprocess. To troubleshoot: '''type m4''' and '''ldd /usr/bin/m4''', also try to run bison with a verbose switch.
 
+ Solution::
+  It turns out (using strace) the bison expects m4 to be in /bin. Here is at least a workaround:
+
+  Exec in Chapter 5a (non-chroot, at `m4` or `bison`)
+  {{{
+  ln -svf ../usr/bin/m4 $LFS/bin/
+  }}}
+
+----
+
+==== tar reports "write error" (Moody, 04.05.2020)
+ (wontfix/non-critical)
+
+ Description::
+  This is caused by using tar in a pipe like
+  {{{
+  tar -tf tarname.tar.xz | head -n1
+  }}}
+  in order to retrieve the directory name of the package. The error is not 'nice', but at the end, its harmless.
+
+ Discussion::
+  Also, when in chroot, tar reports **tar: write error** just like this one discussed ten years ago:  https://www.mail-archive.com/lfs-support@linuxfromscratch.org/msg13073.html
+
   For the '''tar''' issue, is it in a pipe? The mailing list thread concluded that it was related to a change in the way the SIGPIPE signal was handled.
 
-
+ Solution::
+   <none>