On 2019-02-25 22:07 +0100, Pierre Labastie wrote: > On 25/02/2019 19:29, Bruce Dubbs wrote: > > On 2/25/19 12:22 PM, Pei Jia wrote: > > > To whom it may concern: > > > > > > > > > I'm building LFS, so far everything is good, until *Python while > > > constructing a temporary system*. > > > > > > http://www.linuxfromscratch.org/lfs/view/systemd/chapter05/Python.html > > > > > > > > > 1. If I strictly follow what's instructed, I obtained the following > > > *ERROR* messages: > > > > > > /INFO: Could not locate ffi libs and/or headers// > > > ///mnt/lfs/sources/python/Python-3.7.2/Modules/_dbmmodule.c:16:10: fatal > > > error: ndbm.h: No such file or directory// > > > // #include <ndbm.h>// > > > // ^~~~~~~~// > > > //compilation terminated.// > > > //In file included from ./Include/py_curses.h:36,// > > > // from > > > /mnt/lfs/sources/python/Python-3.7.2/Modules/_curses_panel.c:15:// > > > ///usr/include/ncursesw/curses.h:60:10: fatal error: > > > ncursesw/ncurses_dll.h: > > > No such file or directory// > > > // #include <ncursesw/ncurses_dll.h>// > > > // ^~~~~~~~~~~~~~~~~~~~~~~~// > > > //compilation terminated.// > > > ///mnt/lfs/sources/python/Python-3.7.2/Modules/_hashopenssl.c:23:10: fatal > > > error: openssl/evp.h: No such file or directory// > > > // #include <openssl/evp.h>// > > > // ^~~~~~~~~~~~~~~// > > > //compilation terminated.// > > > ///mnt/lfs/sources/python/Python-3.7.2/Modules/nismodule.c:17:10: fatal > > > error: rpc/rpc.h: No such file or directory// > > > // #include <rpc/rpc.h>// > > > // ^~~~~~~~~~~// > > > //compilation terminated.// > > > //In file included from ./Include/py_curses.h:36,// > > > // from > > > /mnt/lfs/sources/python/Python-3.7.2/Modules/_cursesmodule.c:113:// > > > ///usr/include/ncursesw/curses.h:60:10: fatal error: > > > ncursesw/ncurses_dll.h: > > > No such file or directory// > > > // #include <ncursesw/ncurses_dll.h>// > > > // ^~~~~~~~~~~~~~~~~~~~~~~~// > > > //compilation terminated./ > > Those errors prevent building some modules, whose presence is not required at > this stage. So please ignore.
Maybe we should add a <note> or <caution> in Chapter 5 Python 3: <note><para>Some Python modules will fail to build and output error messages. They are unnecessary in this stage and the error messages should be ignored.</para></note> > > > 2. After some investigation, I added up *2 includedirs* as: > > > > > > /./configure --prefix=/tools --without-ensurepip --includedir=/usr/include > > > --includedir=/usr/include/x86_64-linux-gnu/ > > Please don't do that: that would make python link to libraries on the host, so > that it will be unusable in chroot... The reason to use the sed command is exactly NOT to use libraries in /usr/lib and headers in /usr/include. They are known to cause problems building Glibc in Chapter 6. -- Xi Ruoyao <[email protected]> School of Aerospace Science and Technology, Xidian University -- 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
