I got through the first stage of the LFS procedure just fine. The first
pass at compiling glibc-2.3.6 went well, as did compilation of all the
other packages in the toolset. Moving on to the second stage, I set up
the chrooted environment as described in Chapter 6 and went through
several package installations with no hitch. Then, in Section 6.9, I
began to compile glibc-2.3.6. I added glibc-libidn as indicated by the
instructions and applied the prescribed patches, then compiled with
'make'. The compilation failed.
At that point I began suspecting that the glib-libidn package was
faulty, or perhaps one of the patches might be causing trouble. Once
again I deleted out the $LFS/glibc-build directory and the
$LFS/sources/glibc-2.3.6 directory. This time I got a new
glibc-libid-2.3.6.tar.bz2 file from the web site. I repeated all the
prescribed steps, ***but this time did not add a single patch***. I also
did not run the sed scripts. Same failure. I attempted to compile
without adding the glibc-libidn files. Same failure.
Here is the error I received consistently through these attempts:
END { printf "sysdep-subdirs =%s\n", subdirs; \
printf "sysdep-inhibit-subdirs =%s\n", inhibit; \
print "sysd-dirs-done = t" }' \
/dev/null nptl/sysdeps/pthread/Subdirs sysdeps/unix/inet/Subdirs
sysdeps/unix/Subdirs > /glibc-build/sysd-dirs-tmp
/bin/sh: BEGIN { subdirs = ""; inhibit = "" }; /^#/ {
next }; /^[^-]/ { subdirs
= subdirs " " $0 }; /^-/ { inhibit = inhibit " "
substr($0, 2) }; END { printf "sysdep-subdirs =%s\n",
subdirs; printf "sysdep-inhibit-subdirs =%s\n", inhibit;
print "sysd-dirs-done = t" }: No such file or directory
make[1]: *** [/glibc-build/sysd-dirs] Error 127
make[1]: Leaving directory `/sources/glibc-2.3.6'
make: *** [all] Error 2
Finally I attempted to compile glibc with a simple ./configure
statement, no other options set.'make' died again, complaining that the
configuration options did not support threads and I probably wanted to
do that. Actually, I just wanted to get through a compilation without
failure, but there it is.
I guess there is something wrong with my environment. The errors suggest
there are items missing from sysd-dirs and sysdep. Indeed, there are no
such files except for a sysd-tmp file which is completely empty.
Any ideas?
John Reese
Exactly the same errors.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page