On Sat, Feb 01, 2020 at 11:38:13PM -0700, Alan Feuerbacher via blfs-support
wrote:
> On 2/1/2020 8:52 PM, Ken Moffat via blfs-support wrote:
> > As with any 'No such file or directory' : does it exist, and do all
> > the libs it wants to use ? Since you have not managed to enter
> > chroot, add a $LFS prefix when looking at this:
> >
> > ls -l $LFS/usr/bin/env
> >
> > and if it does exist
> >
> > ldd $LFS/usr/bin/env
> >
> > Also, if your shell on the host system is not /bin/bash then other
> > changes might be necessary (e.g. on recent SystemRescueCD, based on
> > Arch, the shell seems to be zsh and passing PS1 doesn't work.
I think Bruce has already pointed the way forward, but you don't
seem to be thinking clearly about what you are doing. ...
> I already checked all that. Nevertheless:
>
> [alan@localhost ~]$ ll /usr/bin/env
> -rwxr-xr-x. 1 root root 54096 Oct 17 01:37 /usr/bin/env
>
> [alan@localhost ~]$ ll /bin/env
> -rwxr-xr-x. 1 root root 54096 Oct 17 01:37 /bin/env
>
> [alan@localhost ~]$ echo $LFS
> /mnt/lfs
>
> [alan@localhost ~]$ ls -l $LFS/usr/bin/env
> ls: cannot access '/mnt/lfs/usr/bin/env': No such file or directory
>
> [alan@localhost ~]$ ldd /usr/bin/env
> linux-vdso.so.1 (0x00007ffe86bfd000)
> libc.so.6 => /lib64/libc.so.6 (0x00007fcc3f5f5000)
> /lib64/ld-linux-x86-64.so.2 (0x00007fcc3f7e5000)
> [alan@localhost ~]$ echo $SHELL
> /bin/bash
>
> Alan
>
In a reply to Bruce you noted that after a reboot fedora doesn't
mount the LFS partitions. Well duh, that is absolutely correct.
If you reboot the host system and want to again build or fix the lfs
system you need to mount it.
All the details above about {/usr,}/bin/env are from your fedora
host, and specifically running ldd against the host is not useful.
I had assumed that /mnt/lfs was mounted. If you get a similar
situation where 'ls' says No such file, check the higher levels -
that would have told you, based on what you said to Bruce, that
/mnt/lfs/usr did not exist. If you then looked at /mnt/lfs you
would, I hope, have seen that the directory was empty, not even a
lost+found entry.
And from that, you should be able to detect that either you ran rm
-rf in /mnt/lfs, or that it is not mounted.
ĸen
--
We had folksingers in the lower bar for six months back home where
I worked. In the end we had to get a man in with a ferret.
-- Polly, in "Interesting Times"
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
