On Mon, Dec 22, 2014 at 9:50 PM, Bruce Dubbs <[email protected]> wrote:

>
> If /tools points to /mnt/lfs/wrk/tools, then when you chroot, it can't
> find /tools/bin, it would need to be /wrk/tools/bin.
>
> I suggest you change the symlink from /tools to /mnt/lfs/tools on the host
> and also, in the host:
>
> cd /mnt/lfs
> mv wrk/tools .
>
> I suppose you could also do 'ln -s wrk/tools /mnt/lfs/tools'
>
>   -- Bruce
>
>
AH!!! That was the problem.. Was staring me at the face and I missed it.

I had the following which I failed to mention:

$ ls -l /mnt/lfs
total 21
drwxr-xr-x   3 root root  1024 Dec 22 02:35 boot
drwxr-xr-x  18 root root  3500 Dec 22 20:21 dev
drwx------   2 root root 16384 Dec 22 02:35 lost+found
dr-xr-xr-x 253 root root     0 Dec 15 00:45 proc
drwxrwxrwt   2 root root    40 Dec 22 20:50 run
dr-xr-xr-x  13 root root     0 Dec 15 13:27 sys
lrwxrwxrwx   1 root root    18 Dec 22 02:37 tools -> /mnt/lfs/wrk/tools
drwxr-xr-x   8 lfs  lfs   4096 Dec 22 02:33 wrk

------------------------------------------

changed to your suggestion using ln -s wrk/tools /mnt/lfs/tools

$ ls -l /mnt/lfs
total 21
drwxr-xr-x   3 root root  1024 Dec 22 02:35 boot
drwxr-xr-x  18 root root  3500 Dec 22 20:21 dev
drwx------   2 root root 16384 Dec 22 02:35 lost+found
dr-xr-xr-x 257 root root     0 Dec 15 00:45 proc
drwxrwxrwt   2 root root    40 Dec 22 20:50 run
dr-xr-xr-x  13 root root     0 Dec 15 13:27 sys
lrwxrwxrwx   1 root root     9 Dec 22 23:51 tools -> wrk/tools
drwxr-xr-x   8 lfs  lfs   4096 Dec 22 02:33 wrk


And that worked. Failed to notice that /mnt/lfs/wrk/tools would be invalid
within chroot.

Thanks for the help!
-- 
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