[SOLVED] Chapter 5.10 Error on Sanity Check

dopaseraoxy · 11-28-2019, 08:39 AM

So this is my first time making LFS. Everything's gone smoothly up until now. I did the install of GCC-9.2.0 pass 2 and everything seemed fine. All commands copy and pasted from the site itself. However when I ran the sanity check, I got this:

Code:

lfs@ksawer-Aspire-A315-21:/mnt/lfs/sources/gcc-9.2.0/build$ echo 'int main(){}' > dummy.c
lfs@ksawer-Aspire-A315-21:/mnt/lfs/sources/gcc-9.2.0/build$ cc dummy.c
/usr/bin/ld: /mnt/lfs/tools/bin/../lib/gcc/x86_64-pc-linux-gnu/9.2.0/../../../../lib/crti.o: unable to initialize decompress status for section .debug_aranges
/usr/bin/ld: /mnt/lfs/tools/bin/../lib/gcc/x86_64-pc-linux-gnu/9.2.0/../../../../lib/crti.o: unable to initialize decompress status for section .debug_aranges
/usr/bin/ld: /mnt/lfs/tools/bin/../lib/gcc/x86_64-pc-linux-gnu/9.2.0/../../../../lib/crti.o: unable to initialize decompress status for section .debug_aranges
/usr/bin/ld: /mnt/lfs/tools/bin/../lib/gcc/x86_64-pc-linux-gnu/9.2.0/../../../../lib/crti.o: unable to initialize decompress status for section .debug_aranges
/mnt/lfs/tools/bin/../lib/gcc/x86_64-pc-linux-gnu/9.2.0/../../../../lib/crti.o: file not recognized: File format not recognized
collect2: error: ld returned 1 exit status
lfs@ksawer-Aspire-A315-21:/mnt/lfs/sources/gcc-9.2.0/build$ readelf -l a.out | grep ': /tools'
readelf: Error: 'a.out': No such file

I'm not quite sure what went wrong or how to fix this. Any help and an explanation would be nice! (Link to where I am in the booklet)

EDIT: Was missing ld in tools/bin. Ran cp /tools/bin/ld-new /tools/bin/ld and it worked. Solved by someone on Facebook.

hazel · 11-28-2019, 01:09 PM

It's trying to link your dummy file with the ld from /usr/bin. That's the host system's ld and it's definitely wrong; it should be using /tools/bin/ld.

My guess is that you didn't carry out the edit specified in this chapter to "Once again, change the location of GCC's default dynamic linker to use the one installed in /tools".

dopaseraoxy · 11-28-2019, 01:25 PM

Quote:

Originally Posted by hazel

It's trying to link your dummy file with the ld from /usr/bin. That's the host system's ld and it's definitely wrong; it should be using /tools/bin/ld.

My guess is that you didn't carry out the edit specified in this chapter to "Once again, change the location of GCC's default dynamic linker to use the one installed in /tools".

Do you mean the symlink? I did that, and then re-did it because I thought it messed up.

Code:

lfs@ksawer-Aspire-A315-21:/mnt/lfs/sources/gcc-9.2.0/build$ ln -sv gcc /tools/bin/cc
'/tools/bin/cc' -> 'gcc'

Or was there an edit to the chapter that I'm unaware of?

hazel · 11-28-2019, 02:57 PM

Here is the section from chapter 5.10.1 of the book that I was referring to. Read it carefully. Did you do all this after untarring the source?

Quote:

Once again, change the location of GCC's default dynamic linker to use the one installed in /tools.

for file in gcc/config/{linux,i386/linux{,64}}.h
do
cp -uv $file{,.orig}
sed -e 's@/lib$64$\?$32$\?/ld@/tools&@g' \
-e 's@/usr@/tools@g' $file.orig > $file
echo '
#undef STANDARD_STARTFILE_PREFIX_1
#undef STANDARD_STARTFILE_PREFIX_2
#define STANDARD_STARTFILE_PREFIX_1 "/tools/lib/"
#define STANDARD_STARTFILE_PREFIX_2 ""' >> $file
touch $file.orig
done

Putting in the cc link is the final stage, after building and installing. Your gcc build probably went wrong right at the beginning.