On 01/07/2015 09:45 PM, hans kaper wrote:
> Op Thu, 01 Jan 2015 15:21:37 +0100 schreef hans kaper <[email protected]>:
> 
>> Op Tue, 23 Dec 2014 06:50:34 +0100 schreef Bruce Dubbs
>> <[email protected]>:
>>
>>> Brent Hostetler wrote:
>>>> I am going through a new build and I am having trouble entering the
>>>> chroot
>>>> after building the toolchain.
>>>
>>>
>>> I suggest you change the symlink from /tools to /mnt/lfs/tools on the
>>> host and also, in the host:
>>>
>>>   -- Bruce
>>>
>>
>> I have the same problem although my starting situation is as Bruce
>> advised and the tools-subdirectory is in /mnt/lfs.
>> Apart from the /wrk-part, the output from ls is as described above.
>> I am building LFS 7.6 from a build-script in /mnt/lfs that calls
>> another script that runs the chroot-call.
>>
>> Any ideas what I do wrong?
>>
>>
>> Hans.
> 
> The problem disappeared by rebuilding the toolchain, but the question
> remains: as root I can cd into /mnt/lfs/tools/bin, I can see the
> binaries, they are executable, I can peek into them, but I cannot run
> them. For instance ./date gives "no such file or directory".
> 
> I am grateful for suggestions to better understand what is going on.
> 
> 
> 
> Hans.

This is a problem with misconfigured dynamic linker that doesn't exist
or is broken.

Find out with: readelf -e /path/to/binary | grep interpreter

For files in /tools, it should return the dynamic linker that's being
used and it should be the same one specified in the "Caution" box on the
bottom of the GCC Pass2 in chapter 5.

-- 
Note: My last name is not Krejzi.

Attachment: signature.asc
Description: OpenPGP digital signature

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Reply via email to