Hi

another thing I have just noticed you should be in dir /mnt/lfs

you look like you are in $ source

OK yeah that was a typo.

When i login as lfs i get this;



nathan@ubuntu:~$ su - lfs
Password:
No command 'unmask' found, did you mean:
Command 'unmass' from package 'unmass' (universe)
unmask: command not found

I dont understand wgat its telling me. When did i type unmass or unmask? at first i thought i had made a mistake eariler on but i went back and double checked and found nothing.

ok so here is what i get when i try to binutils-build;

lfs@ubuntu:~$ mkdir -v ../binutils-build
Command 'mkdir' is available in '/bin/mkdir'
The command could not be located because '/bin' is not included in the PATH environment variable.
mkdir: command not found
lfs@ubuntu:~$

how is mkdir not found? mkdir works fine when logged in as my normal user, just not as lfs. Again i wnt back and deleted the old lfs user and started again, making sure to enter all command right but i was unable to fix anything. Again i understand what the computer is telling me i just dont know how to fix it.

Ok so with a little experimentation i have found that with lfs user even simple commands do not exist, ie. ls. I am for some reason able to cd ../binutils-build.

unmask isn't a linux command, umask is. You probably made one or more mistakes in your lfs environment files.

Execute these 2 commands as root user and post the resulting outcome:

nathan@ubuntu:~$ sudo cat /home/lfs/.bash_profile
exec env -i HOME=$HOME TERM=$TERM PS1=' \u:\w\$ ' /bin/bash
nathan@ubuntu:~$ cat /home/lfs/.bashrc
set +h
unmask 022
LFS=/mnt/lfs
LC_ALL=POSIX
LFS_TGT=$(uname -m)-lfs-linux-gnu
PATH=/tools/bin:/bin/usr/bin
export LFS LC_ALL LFs_TGT PATH


Oh i see. ok im gonna go back and change "unmask 022" to "umask 022"

That should be umask not unmask.....

EDIT: You did notice the typo.........

ok i think i have fixed that issue, but i still have an issue trying to do the same thing.

lfs@ubuntu:~$ mkdir -v ../binutils-build
mkdir: cannot create directory `../binutils-build': File exists
lfs@ubuntu:~$ cd ../binutils-build
lfs@ubuntu:/home/binutils-build$ ../binutils-2.22/configure \
> --target=$LFS_TGT --prefix=/tools \
> --disable-nls --disable-werror
-su: ../binutils-2.22/configure: No such file or directory
lfs@ubuntu:/home/binutils-build$

I see other errors:
- PATH=/tools/bin:/bin/usr/bin -> PATH=/tools/bin:/bin:/usr/bin
- export LFS LC_ALL LFs_TGT PATH -> export LFS LC_ALL LFS_TGT PATH

........

I tried to build binutils in "cd /mnt" and i get this;

lfs@ubuntu:/mnt$ mkdir -v ../binutils-build
mkdir: cannot create directory `../binutils-build': Permission denied
lfs@ubuntu:/mnt$ sudo mkdir -v ../binutils-build
[sudo] password for lfs:
lfs is not in the sudoers file. This incident will be reported.
lfs@ubuntu:/mnt$

ok i will fix those errors, but i copied and pasted? Are those errors in the LFS book or is it just expected that i know not to put that?

Is that a question? If you actually copy-> pasted then you have a big problem......

Those errors are not in the book, which you can check yourself.

Do you actually visually check what you copy and paste (type)? If you would have you would have noticed these typo's.

Yes i double check when i type but sometimes i miss stuff. And i have it all fixed. i thought i had sent you the code from the corrected (copied and pasted) code that i imputed, but i see that i did not. OK so i am back to the same issue. i have entered all the code correctly and i am still experiencing the same issue.

lfs@ubuntu:/home/binutils-build$ ../binutils-2.22/configure \
> --target=$LFS_TGT --prefix=/tools \
> --disable-nls --disable-werror
bash: ../binutils-2.22/configure: No such file or directory



What am i doing wrong now? do u want me to go through the whole process of making the lfs user up until now and copy and past all the code??

You were not in the proper directory when you began section 5.4.1. As it is for all packages, untar the binutils tarball and change to the directory created by that. Then begin the commands in 5.4.1. When you do it that way, you will not be down in the /home directory of the lfs user. You will be down in the /sources directory in $LFS.