lfs 10.1 | Entering the Chroot Environment | Ubuntu 20.04 | '/usr/bin/env’: Not a directory
Hello,
Host distribution: Ubuntu 20.04 LFS book version: 10.1 Section where the problem was encountered: 7.4. Entering the Chroot Environment Error: Code:
root@farhat-pc:/mnt/lfs# chroot "$LFS" /usr/bin/env -i \ Code:
root@farhat-pc:/mnt/lfs# ls -lah usr/bin/env I am sure that I have followed the two previous section 7.2 && 7.3 Any hint please? |
I'm experiencing the same thing, building on top of OpenSuse.
https://www.linuxquestions.org/quest...ry-4175692690/ |
is LFS set correctly?
|
Quote:
|
is $LFS actually mounted?
|
what is at $LFS/dev , $LFS/proc etc ie are the virtual systems mounted, what are the mount options for $LFS
|
Quote:
https://www.linuxquestions.org/quest...ry-4175692690/ It's a bit odd that both of us, on the same day, ran into the same issue, at the same exact point in the process. |
I had a similar problem when 1st using the new build system, it was the lib folders, are you using /lib64 and /usr/lib64 ( presuming a 64 bit machine ) or are you using /lib and /usr/lib ?
On my system /lib is symlink to /lib64 and /usr/lib is symlink to /usr/lib64. |
Quote:
So, it appears that I'm using /lib and /usr/lib for all but the following: Inside /mnt/lfs/lib64 are ld-linux-x86_64.so.2 and ld-lsb-x86-64.so.3 /mnt/lfs/usr/lib64 contains several libstdc++ libraries What do you think is the best way to proceed from here since there are libs in both? |
My only fix was to start from scratch, and make sure the links were in at the begining sorry :(
|
Quote:
|
probably this.... chapter 5.5.1
Code:
case $(uname -m) in |
Quote:
I've now run into this: Code:
chroot: failed to run command ‘/usr/bin/env’: Too many levels of symbolic links |
Thank you all,
I restart the process from the beginning and the issue has been resolved(It took me ~2-3 hours) |
You should have made those symlinks in chapter 5.5 and not afterwards.
Unfortunately this means redoing chapter 5. |
All times are GMT -5. The time now is 09:41 AM. |