Question about LFS 7.7 Chapter 6.17

Baihua · 04-06-2015, 04:03 PM

According to the instruction, I made cc a symlink to /usr/bin/gcc using the command

Code:

ln -sv gcc /usr/bin/cc

and when I went to /usr/bin to do

Code:

ls -la

, I do see that the symlink is created. However, the sanity check

Code:

echo 'main(){}' > dummy.c
cc dummy.c -v -Wl,--verbose &> dummy.log
readelf -l a.out | grep ': /lib'

gives no output.

However, when I tried the above with "gcc" instead of "cc", everything, including the subsequent outputs expected from the sanity checks, came about correctly.

Any idea why this is happening?

veerain · 04-07-2015, 01:09 AM

Post the output of:

Code:

ls -l /usr/bin/cc
ls -l /usr/bin/gcc
which gcc

Baihua · 04-07-2015, 11:02 AM

Code:

ls -l /usr/bin/cc
lrwxrwxrwx 1 root root 12 Apr  6 20:56 /usr/bin/cc -> /usr/bin/gcc

Code:

ls -l /usr/bin/gcc
-rwxr-xr-x 3 root root 2537709 Apr  6 17:18 /usr/bin/gcc

"which" command is not supported yet since I am in the chroot environment.

veerain · 04-07-2015, 12:51 PM

What's your PATH environment variable value?

Code:

echo $PATH

Baihua · 04-07-2015, 02:02 PM

I think I know what the problem is:

when I compile with gcc, the readelf will give this output:

Code:

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

when compiling with cc, the readelf has this line as:

Code:

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

and that's why the

Code:

grep ': /lib'

did not get anything when compiling with "cc"

And I believe that the subsequent outputs that did not appear have similar problems

Now the question is:

why would cc try to find the interpreter from /tools/lib? And would this be a problem in the future?

veerain · 04-07-2015, 09:28 PM

So answer is why you run cc from /tools/bin? Why have you not set /tools/bin path at the end PATH Environment Variable while doing chroot? Check your executable search path. And do follow the book correctly.