LinuxQuestions.org - [SOLVED] Possible oddness with 7.4rc1

- Linux From Scratch (https://www.linuxquestions.org/questions/linux-from-scratch-13/)

- - Possible oddness with 7.4rc1 (https://www.linuxquestions.org/questions/linux-from-scratch-13/possible-oddness-with-7-4rc1-4175475398/)

Possible oddness with 7.4rc1

built and booted t4.4rc1 seems ok but going back over some logs I found that the dummy.log created at

http://www.linuxfromscratch.org/lfs/...adjusting.html

Gives some odd results like so:

Code:

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

/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib64/crt1.o succeeded

/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib64/crti.o succeeded

/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib64/crtn.o succeeded

 /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/include-fixed

 /usr/include

SEARCH_DIR("/usr/x86_64-unknown-linux-gnu/lib64")

SEARCH_DIR("/usr/local/lib64")

SEARCH_DIR("/lib64")

SEARCH_DIR("/usr/lib64")

SEARCH_DIR("/usr/x86_64-unknown-linux-gnu/lib")

SEARCH_DIR("/usr/local/lib")

SEARCH_DIR("/lib")

SEARCH_DIR("/usr/lib");

attempt to open /lib64/libc.so.6 succeeded

found ld-linux-x86-64.so.2 at /lib64/ld-linux-x86-64.so.2

There seems to be no cross contamination with the host but some stuff seems to be in odd places according to the logfile I have checked and crt* are in /usr/lib where they should be, is this a problem or just genereal weirdness?

Quote:

Originally Posted by Keith Hedger (Post 5019362)

built and booted t4.4rc1 seems ok but going back over some logs I found that the dummy.log created at

http://www.linuxfromscratch.org/lfs/...adjusting.html

Gives some odd results like so:

Code:

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

/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib64/crt1.o succeeded

/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib64/crti.o succeeded

/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib64/crtn.o succeeded

What does readlink -f /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib64/crtn.o show?

The link points to the correct place ie /usr/lib/crtn.o
As I said it all seems to be working and I am now building Xorg fine ( in chroot ), I don't see why these somwhat odd paths seem to be there.

Quote:

Originally Posted by Keith Hedger (Post 5019498)

The link points to the correct place ie /usr/lib/crtn.o
As I said it all seems to be working and I am now building Xorg fine ( in chroot ), I don't see why these somwhat odd paths seem to be there.

For quite some time, the GNU Compiler Collection has used the "indirection" of paths to resolve the location of object and library files. See the output of gcc -print-search-dirs for the extensive use of "double-dot" paths.

I get

Code:

install: /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/

programs: =/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/:/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/:/usr/lib/gcc/x86_64-unknown-linux-gnu/:/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/:/usr/lib/gcc/x86_64-unknown-linux-gnu/:/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../x86_64-unknown-linux-gnu/bin/x86_64-unknown-linux-gnu/4.8.1/:/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../x86_64-unknown-linux-gnu/bin/

libraries: =/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/:/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../x86_64-unknown-linux-gnu/lib/x86_64-unknown-linux-gnu/4.8.1/:/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../x86_64-unknown-linux-gnu/lib/../lib64/:/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../x86_64-unknown-linux-gnu/4.8.1/:/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib64/:/lib/x86_64-unknown-linux-gnu/4.8.1/:/lib/../lib64/:/usr/lib/x86_64-unknown-linux-gnu/4.8.1/:/usr/lib/../lib64/:/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../x86_64-unknown-linux-gnu/lib/:/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../:/lib/:/usr/lib/

I still don't know if I can ignore this or if it will bite me in the a*** later on, any thougts?

Quote:

Originally Posted by Keith Hedger (Post 5019524)

I still don't know if I can ignore this or if it will bite me in the a*** later on, any thougts?

Try this to assure yourself that it's all good:

Code:

for path in $(gcc -print-search-dirs | awk '/libraries:/ { sub("=", ""); print $2 }' | tr ':' ' '); 

    do readlink -f $path; 

done | sort -u

And to really prove it, go to a known good host system using GCC 4.X.X and repeat the same command. It's normal.

I get

Code:

/lib

/usr/lib

/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1

On both my present system and the new 7.4rc1 ( allowing for the gcc version ) so I guess that means everything's OK.

I'll mark this solved.