On 12/20/06, Hubert Gabler <[EMAIL PROTECTED]> wrote: > > > From here, it looks as if you'll need to begin again. At the start > > of chapter 6, the only available libraries (and programs) are in > > /tools, so (for example) /lib/ld-linux.so.2 cannot be used. > > > > The instructions in section 5.7 are key to this. When you get to > > that stage, please review the results of the manipulations to ld, > > and similarly inspect the specs file to make sure that the changes > > have been made.
Just to reiterate, the sanity check at the end of 5.7 is really important. > I am afraid that starting from scratch again would not solve the > problem. As I mentioned in my first posting I tried to install LFS on 2 > different hosts and ended at the same error statement. Moreover I had > _typed_ the commands on one PC and used _cut-and-paste_ (from the > pdf-manual) on the other. So it seems very unlikely that I did the same > typo twice. This is an extremely subtle part of the book. It is very possible that something went wrong twice. Just to make sure we're talking about the same problem, what is the output of this command? $ readelf -l /tools/bin/gcc | grep ld-linux It should say "/tools/lib/ld-linux.so.2". I'd wager that it says "/lib/ld-linux.so.2" for you. > I wonder if it is an unwanted side-effect of my operating system (Ubuntu > 6.06). This thought came to me when I noticed this: > The error message when executing compile was "/tools/bin/gcc: No such > file or directory". From inside chroot I changed to /tools/bin and did > list -l. The listing shows that gcc is here, owned by root. When I from > the same directory type gcc -v the result is: "file not found" - > although it is here!! In other words, I - as root - am not permitted to > run gcc, owned by root. It's probably not a side-effect of the host. The error message is a red herring. What's really happening is that /tools/bin/gcc can't be executed because it's trying to use a dynamic linker that doesn't exist (/lib/ld-linux.so.2). When it completely fails to execute (even to start), this bogus error comes back to you. If you had a tool like strace in the chroot, you could see where the real error was. As a quick workaround, just make a symbolic link to the tools dynamic linker. $ ln -sv /tools/lib/ld-linux.so.2 /lib Can you execute gcc now? -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
