Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
[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?
[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
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?
What does readlink -f /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib64/crtn.o show?
Distribution: Void, Linux From Scratch, Slackware64
Posts: 3,150
Original Poster
Rep:
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.