I wasn't sure whether to send this to lfs-support or lfs-dev. Since I'm not a developer on LFS, I guessed the former. Apologies if my guess is unhelpful.
I built LFS using jhalfs and the 8.2 version of the book on a machine with an Intel G860 processor. The configure script for libffi guessed wrong about the processor's capabilities, causing Python 3 to crash with an invalid instruction exception. I fixed this by changing the jhalfs script 115_libffi to let gcc determine the architecture rather than the configure script itself: ./configure --prefix=/usr --disable-static --with-gcc-arch=native See here for reference: http://linuxfromscratch.org/lfs/view/development/chapter06/libffi.html I would like to ask that the developers consider making this change to the LFS book. This might possibly cause incorrect behavior on other CPU types, although I would think gcc would do a better job than this buggy script. So at the very least, it would be helpful to mention this problem and solution on the libffi step (where the problem originates) and the Python 3 step (where it manifests itself as an "invalid instruction" exception). It took me a couple of days to figure this out because I kept thinking the problem was in Python 3. Now that I know what happened, search shows that at least one other person has been bitten by this (Celeron G530 in their case): http://lists.linuxfromscratch.org/pipermail/lfs-support/2018-May/052008.html Thanks for all the great work you guys do! This is a fantastic educational resource. - Don
-- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
