On Mon, Dec 17, 2018 at 06:25:00PM -0500, ian wrote: > Hi All, > > Following the guide to a tee I get all the way to the chroot into th system > to build glibc. > > Running configure as per: > > CC="gcc -isystem $GCC_INCDIR -isystem /usr/include" \ ../configure > --prefix=/usr \ --disable-werror \ --enable-kernel=3.2 \ > --enable-stack-protector=strong \ l:ibc_cv_slibdir=/lib >
Typo in that last item (l:ibc_...) and I've never seen the backslashes shown like that - in case you did not know, they are a line-continuation mark and should be the last character on a line. So, when you use the up-arrow to scroll back through your commands, or use 'history', you will not see them. The typo is probably irrelevant to this, but misunderstanding backslashes might have contributed to the errors. More at the end. > I get the following: > > checking version of makeinfo... v. ?.??, bad Another example of the same error. > checking for sed... sed > checking version of sed... 4.5, ok > checking for gawk... gawk > checking version of gawk... v. ?.??, bad > checking for bison... bison > checking version of bison... 3.0.5, ok > checking if gcc -isystem /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include > -isystem /usr/include is sufficient to build libc... yes > checking for nm... nm > checking for python3... no > checking for python... no > configure: error: > *** These critical programs are missing or too old: gawk > *** Check the INSTALL file for required versions. > (lfs chroot) root:/sources/glibc-2.28/build# > > It seems gawk fails for what ever the reason? > > I have gone through the whole process twice from scratch - all tests and > builds seem successful. All tests ? If you mean the tests to check that your environment is set up correctly and the host packages are present, that is good. But if you meant that you ran 'make check' in chapter 5, that would be a waste of time. > > Too, I have looked through the material on the site and can't seem to find > any reference to others encountering the same issue. > > When I run /tools/bin/gawk I from the cli I get: > > (lfs chroot) root:/sources/glibc-2.28/build# /tools/bin/gawk > bash: /tools/bin/gawk: No such file or directory > (lfs chroot) root:/sources/glibc-2.28/build# > > When run outside the chroot jail I get a working gawk. > > Would be grateful for any help. > > Kindly, > > Ian > This is the classic "Any no such file" which used to be documented somewhere on the site, and maybe still is. If you run 'ldd' on /tools/bin/gawk, you will see that one or more of the libraries it uses is in /usr on the host, instead of in /tools/, and in chroot it will not be found. One cause can be interrupting the build and shuttng down, then not reinstating the LFS user's environment when resuming. Another cause might be missing /tools when keying in a prefix in chapter 5, and I'm sure there are a number of other possible reasons. ĸen -- I'm saving up 22 shillings and 10 pence (almost a pound!) per week to buy an ARM-13. http://www.antipope.org/charlie/blog-static/2018/11/brexit-means-brexit.html -- 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
