Changes between Version 5 and Version 6 of cross-chap5


Ignore:
Timestamp:
05/05/2020 12:23:06 PM (18 months ago)
Author:
thomas
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • cross-chap5

    v5 v6  
    6161=== Phenomenon on ArchLinux
    6262
    63  Issue:: Moody, 04.05.2020:
     63==== glibc in ch6 failes with "bison: m4 subprocess failed" (Moody, 04.05.2020)
     64  (solved/workaround)
    6465
    6566  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:
     
    9293}}}
    9394
    94   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
    95 
    9695  This all does not happen when running the build on a LFS-SVN host.
    9796
    98  Solution::
    99   <currently none>
    10097 Discussion::
    10198  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.
    10299
     100 Solution::
     101  It turns out (using strace) the bison expects m4 to be in /bin. Here is at least a workaround:
     102
     103  Exec in Chapter 5a (non-chroot, at `m4` or `bison`)
     104  {{{
     105  ln -svf ../usr/bin/m4 $LFS/bin/
     106  }}}
     107
     108----
     109
     110==== tar reports "write error" (Moody, 04.05.2020)
     111 (wontfix/non-critical)
     112
     113 Description::
     114  This is caused by using tar in a pipe like
     115  {{{
     116  tar -tf tarname.tar.xz | head -n1
     117  }}}
     118  in order to retrieve the directory name of the package. The error is not 'nice', but at the end, its harmless.
     119
     120 Discussion::
     121  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
     122
    103123  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.
    104124
    105 
     125 Solution::
     126   <none>