I have an Ubuntu Studio 18.04 as a host, and an LFS version 9.0 as a
guide via HTML. I have reached stage 6.9.1 ("glibc") and despite all
efforts to determine the source of this issue, I cannot solve the
infinite loop issue of the glibc steps. I have routed the output to a
log file and taken what appears to be the content of the loop. I also
have the Makefile, which is rather brief and to-the-point. In reference
to an online discussion about the issue, I downloaded a different
version of glibc to see if it made a difference. It seems that it did
not. (The change was made from 2.30 to 2.32)
I edited the log file contents slightly to include comments
("********") about the beginning and end points of the loop. I also
isolated what appears to be the command ("sed") that is triggering it.
Here is the log file text:
*********** Beginning of infinite loop point *********************
rm -f /sources/glibc-2.32/build/jmp_buf-ssp.h.dT
mv -f /sources/glibc-2.32/build/jmp_buf-ssp.h.dT2
/sources/glibc-2.32/build/jmp_buf-ssp.h.d
mv -f /sources/glibc-2.32/build/jmp_buf-ssp.hT
/sources/glibc-2.32/build/jmp_buf-ssp.h
/usr/bin/install -c -m 644 ../include/limits.h /usr/include/limits.h
python3 -B ../scripts/gen-as-const.py --cc="gcc
-ffile-prefix-map=/tools=/usr -std=gnu11 -fgnu89-inline -g -O2 -Wall
-Wwrite-strings -Wundef -fmerge-all-constants -frounding-math
-fstack-protector-strong -Wstrict-prototypes -Wold-style-definition
-fmath-errno -ftls-model=initial-exec -I../include
-I/sources/glibc-2.32/build/setjmp -I/sources/glibc-2.32/build
-I../sysdeps/unix/sysv/linux/i386/i686 -I../sysdeps/i386/i686/nptl
-I../sysdeps/unix/sysv/linux/i386
-I../sysdeps/unix/sysv/linux/x86/include
-I../sysdeps/unix/sysv/linux/x86 -I../sysdeps/x86/nptl
-I../sysdeps/i386/nptl -I../sysdeps/unix/sysv/linux/include
-I../sysdeps/unix/sysv/linux -I../sysdeps/nptl -I../sysdeps/pthread
-I../sysdeps/gnu -I../sysdeps/unix/inet -I../sysdeps/unix/sysv
-I../sysdeps/unix/i386 -I../sysdeps/unix -I../sysdeps/posix
-I../sysdeps/i386/i686/fpu/multiarch -I../sysdeps/i386/i686/fpu
-I../sysdeps/i386/i686/multiarch -I../sysdeps/i386/i686
-I../sysdeps/i386/fpu -I../sysdeps/x86/fpu -I../sysdeps/i386
-I../sysdeps/x86 -I../sysdeps/wordsize-32
-I../sysdeps/ieee754/float128 -I../sysdeps/ieee754/ldbl-96/include
-I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/dbl-64
-I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754 -I../sysdeps/generic
-I.. -I../libio -I. -nostdinc -isystem
/usr/lib/gcc/i686-pc-linux-gnu/9.2.0/include -isystem
/usr/lib/gcc/i686-pc-linux-gnu/9.2.0/include-fixed -isystem
/usr/include -D_LIBC_REENTRANT -include
/sources/glibc-2.32/build/libc-modules.h -DMODULE_NAME=libc -include
../include/libc-symbols.h -DTOP_NAMESPACE=glibc
-DGEN_AS_CONST_HEADERS \
-MD -MP -MF /sources/glibc-2.32/build/jmp_buf-ssp.h.dT \
-MT '/sources/glibc-2.32/build/jmp_buf-ssp.h.d
/sources/glibc-2.32/build/jmp_buf-ssp.h'" \
../sysdeps/unix/sysv/linux/x86/jmp_buf-ssp.sym >
/sources/glibc-2.32/build/jmp_buf-ssp.hT
******* last command of infinite loop? ***********
sed -e 's@ /sources/glibc-2\.32/build/@ $(common-objpfx)@g' -e
's@^/sources/glibc-2\.32/build/@$(common-objpfx)@g' -e 's@ *\.\.\/\([^
\]*\)@ $(..)\1@g' -e 's@^\.\.\/\([^ \]*\)@$(..)\1@g' \
/sources/glibc-2.32/build/jmp_buf-ssp.h.dT >
/sources/glibc-2.32/build/jmp_buf-ssp.h.dT2
********* End of infinite loop point: ***************
rm -f /sources/glibc-2.32/build/jmp_buf-ssp.h.dT
mv -f /sources/glibc-2.32/build/jmp_buf-ssp.h.dT2
**************************************************** end of log file
text ************
Comment is invited.
Brian
--
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
