No output for sanity check in Glibc-2.26 chapter 5.7

parotta36 · 01-19-2018, 11:04 AM

When I performed the sanity check,

Code:

echo 'int main(){}' > dummy.c
$LFS_TGT-gcc dummy.c
readelf -l a.out | grep ': /tools'

the expected output is,

Code:

[Requesting program interpreter: /tools/lib/ld-linux.so.2]

There was no output for me. when I tried readelf without grep,
I got

Code:

[Requesting program interpreter: tools/lib64/ld-linux-x86-64.so.2]

The tools directory doesn't seem to start from root. How do I resolve this?

business_kid · 01-20-2018, 05:10 AM

if your /tools isn't in /, put in a symlink.

Code:

one -sf /full/path/to/tools /tools

parotta36 · 01-20-2018, 06:46 AM

one? command not found

BTW, so the problem is, that the tools in LFS is not linked to /tools?
And also, will all the config in $LFS/tools reflect in /tools once linked?

I tried

Code:

ln -sf $LFS/tools /tools

even from root, and it didn't work.

Keith Hedger · 01-20-2018, 08:00 AM

yes the link is linking the tools folder not the individual tools, creating this link is one of the earlier things the lfs book says todo, ALWAYS read the book !

parotta36 · 01-20-2018, 02:02 PM

Of course I executed the command. I don't know how or why it didn't link.
I'm stuck right now. ln also didn't work. Please help.

Keith Hedger · 01-20-2018, 02:33 PM

this link needs to be made as root.

parotta36 · 01-21-2018, 06:13 AM

The folders are linked. But I still keep getting the same error.

Code:

[Requesting program interpreter: tools/lib64/ld-linux-x86-64.so.2]

Keith Hedger · 01-21-2018, 06:32 AM

I would suggest starting from scratch as you are near the begining of chap 5, delete the tools folder AND the symlink in /, start again and check that all the commands have completed properly especialy the /tools symlink, you can use the readlink or file command to check where a link is pointing to.

parotta36 · 01-22-2018, 11:35 AM

Yes, I restarted my build as suggested. The file links just as before. I verified it using the Dolphin browser[I use Slackware] and I can confirm that it is linked. But when I use ls -l it didn't show the link.
This doesn't seem to be a problem right now.
But again, while performing the sanity check,

Code:

lfs:/mnt/lfs/sources/glibc-2.26/build$ echo 'int main(){}' > dummy.c
lfs:/mnt/lfs/sources/glibc-2.26/build$ $LFS_TGT-gcc dummy.c
/mnt/lfs/tools/bin/../lib/gcc/x86_64-lfs-linux-gnu/7.2.0/../../../../x86_64-lfs-linux-gnu/bin/ld:
cannot find crt1.o: No such file or directory
/mnt/lfs/tools/bin/../lib/gcc/x86_64-lfs-linux-gnu/7.2.0/../../../../x86_64-lfs-linux-gnu/bin/ld:
cannot find crti.o: No such file or directory
collect2: error: ld returned 1 exit status
lfs:/mnt/lfs/sources/glibc-2.26/build$ readelf -l a.out | grep ': /tools'
readelf: Error: 'a.out': No such file

Th bashrc and bash_profile files.

Code:

lfs:/mnt/lfs/sources/glibc-2.26/build$ cat ~/.bash_profile
exec env -i HOME=$HOME TERM=$TERM PS1='\u:\w\$ ' /bin/bash
lfs:/mnt/lfs/sources/glibc-2.26/build$ cat ~/.bashrc      
set +h
umask 022
LFS=/mnt/lfs
LC_ALL=POSIX
LFS_TGT=$(uname -m)-lfs-linux-gnu
PATH=/tools/bin:/bin:/usr/bin
export LFS LC_ALL LFS_TGT PATH

Code:

lfs:/mnt/lfs/sources/glibc-2.26/build$ find -L /tools -name "crt1.o"
/tools/lib/crt1.o
/tools/lib64/crt1.o

Output of version_check.s

Code:

bash-4.3# /host/version_check.sh 
bash, version 4.3.46(1)-release
/bin/sh -> /bin/bash
Binutils: version 2.26.20160125
bison (GNU Bison) 3.0.4
yacc is bison (GNU Bison) 3.0.4
bzip2,  Version 1.0.6, 6-Sept-2010.
Coreutils:  8.25
diff (GNU diffutils) 3.3
find (GNU findutils) 4.4.2
GNU Awk 4.1.3, API: 1.1 (GNU MPFR 3.1.4, GNU MP 6.1.1)
/usr/bin/awk -> /bin/gawk-4.1.3
gcc (GCC) 5.3.0
g++ (GCC) 5.3.0
(GNU libc) 2.23
grep (GNU grep) 2.25
gzip 1.8
Linux version 4.4.14 (root@hive64) (gcc version 5.3.0 (GCC) ) #2 SMP Fri Jun
24 13:38:27 CDT 2016
m4 (GNU M4) 1.4.17
GNU Make 4.1
GNU patch 2.7.5
Perl version='5.22.2';
sed (GNU sed) 4.2.2
tar (GNU tar) 1.29
texi2any (GNU texinfo) 6.1
xz (XZ Utils) 5.2.2

Keith Hedger · 01-22-2018, 02:16 PM

If ls is not showing the link then it has NOT been created properly try:

Code:

readlink /tools

If the output points to anywhere other than your tools folder then you have a problem.

PLEASE NOTE:
"This doesn't seem to be a problem right now." -> WRONG!!!

When presented with ANY error while building the tool chain WILL make for a fubar'ed tool chain and ultimately a broken system, you MUST fix problems as they appear or you you will never get a working LFS system.

parotta36 · 01-23-2018, 07:12 AM

Yes, thanks. I can confirm that it is linked.
Now how to rectify the sanity check error?