On 2018-12-18 3:24 p.m., Pierre Labastie wrote:
On 18/12/2018 00:25, 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
I get the following:
checking version of makeinfo... v. ?.??, bad
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.
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.
Looks like, at some point, /tools was not pointing to /mnt/lfs/tools.
Thanks Ken, Pierre,
I am going to go through this from scratch again - one last time :/
(perhaps).
I can't be certain that the mount point (thx Pierre) was existant the
second time around.
Will let this list know...
So first, check that:
outside chroot: "ls -l /tools"
if you do not obtain something like:
lrwxrwxrwx 1 root root 14 déc. 18 21:15 /tools -> /mnt/lfs/tools
Go back to 4.2. Creating the $LFS/tools directory (issue "echo $LFS" first to
check that the LFS variable is set), and start over. You may ned to issue:
"rm -rf /tools" first
If you do obtain the above output, still outside chroot:
ls -l /tools/bin | grep gawk. You should obtain (up to a change in time):
lrwxrwxrwx 1 root root 4 nov. 22 14:45 awk -> gawk
-rwxr-xr-x 2 root root 3006216 nov. 22 14:45 gawk
-rwxr-xr-x 2 root root 3006216 nov. 22 14:45 gawk-4.2.1
Then (after checking LFS):
ls -l $LFS/tools/bin
If everything's OK, enter chroot (check LFS first, did I say that already?),
then:
ls -l /tools/bin | grep gawk
and you should see the same output...
Do not forget to mount /mnt/lfs, of course...
That's all I can think of.
Pierre
--
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
