On Fri, 2020-04-03 at 10:25 +0200, 🦁 Martin Wagner wrote: > Hello, > > creating a new LFS on an ARM (aarch64) System (Rockpro64 with DietPi- > distribution) stops on compiling GCC in chapter 5.10. (GCC-9.2.0 - > Pass 2) with an Error 1: > > build/genautomata.o build/rtl.o build/read-rtl.o build/ggc-none.o > build/vec.o build/min-insn-modes.o build/gensupport.o build/print- > rtl.o build/hash-table.o build/sort.o build/read-md.o build/errors.o > ../build-aarch64-unknown-linux-gnu/libiberty/libiberty.a -lm > build/genautomata ../../gcc/common.md > ../../gcc/config/aarch64/aarch64.md \ > insn-conditions.md > tmp-automata.c > build/genautomata: /lib/aarch64-linux-gnu/libm.so.6: version > `GLIBC_2.29' not found (required by build/genautomata) > Makefile:2328: recipe for target 's-automata' failed > make[2]: *** [s-automata] Error 1 > make[2]: Leaving directory '/mnt/USB_LFS/sources/gcc- > 9.2.0/build_2/gcc' > Makefile:4330: recipe for target 'all-gcc' failed > make[1]: *** [all-gcc] Error 2 > make[1]: Leaving directory '/mnt/USB_LFS/sources/gcc-9.2.0/build_2' > Makefile:960: recipe for target 'all' failed > make: *** [all] Error 2 > lfs@DietPi:/mnt/USB_LFS/sources/gcc-9.2.0/build_2$ > > > This error is independent if I use GlibC 2.31 or 2.29 for compiling. > > The host system itself has libc-2.24/libm-2.24 > > build/genautomata: /lib/aarch64-linux-gnu/libm.so.6: version > `GLIBC_2.29' not found (required by build/genautomata) > Makefile:2328: recipe for target 's-automata' failed > > I'm not shure, why compiling with access to the hostsystem > "/lib/aarch64-linux-gnu/libm.so.6"? > > > Any ideas fixing this ? > >
I have no experience with something other than i386/amd64, but it looks like the genautomata executable has been linked to the new glibc (as it should), but tries to load the host glibc (which is wrong). What was the output of the sanity check on the glibc page? Haven't you forgotten the --with-sysroot switch on binutils pass2? Can you run the sanity check again, and check it gives the good answer? You may want to try gcc -v dummy.c (from the sanity check), and inspect the result for something like SEARCH PATH. You may also try to specify CC_FOR_BUILD=/usr/bin/gcc in addition to the other settings before configure. But this should not be needed. 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
