============================================================
root:/sources/coreutils-8.21# su nobody -s /bin/bash -c "PATH=$PATH make RUN_EXPENSIVE_TESTS=yes check"
GEN public-submodule-commit
make check-recursive
make[1]: Entering directory `/sources/coreutils-8.21'
Making check in po
/bin/sh: line 17: cd: po: Not a directory
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/sources/coreutils-8.21'
make: *** [check] Error 2

=============================================================

deleted the folder coreutils-8.21 and extracted it again (did twice) compiles ok without errors but the check using 'nobody' gives error stated above ----HELP NEEDED I AM NEW IN THIS AND CURRENTLY BUILDING LFS SO THAT I CAN GO FOR EMBEDDED LINUX AFTERWARDS
Thanks in advance

Could it be that your downloaded coreutils package is corrupt?

Is the po directory present when you unpack coreutils? (It should be)

There's no need to shout......

@druuna

the package is not corrupt it compiled without errors downloaded the package from the site mentioned in LFS. By the way the error occurs only when I try to test as a 'nobody' user su nobody -s /bin/bash -c "PATH=$PATH make RUN_EXPENSIVE_TESTS=yes check" it occurred again in 6.33 Bash-4.2 when then book says to test as 'nobody' user

That doesn't prove anything.

Is coreutils-8.21.tar.xz' MD5 sum as mentioned in the book (MD5 sum: 065ba41828644eca5dd8163446de5d64)?

Is user nobody present? You should have created it here: 6.6. Creating Essential Files and Symlinks (the cat > /etc/passwd ..... part).

Yeah I created the user at that point but I cant be sure about MD5 however I downloaded the package from the URL path that was mentioned in LFS. I have installed it and now I am installing the rest can you tell if it can cause problems in future??

Just check the correctness of the file (md5sum coreutils-8.21.tar.xz).

There's no way of knowing. The tests were not run so the coreutils commands might not be correct. You have a list of installed commands, if any of those are giving you problems you know something is wrong.

On the other hand: All might be functioning correctly.

I checked the md5sum its same as mentioned in the book

@druuna

I think its a problem with the user 'nobody' any ideas???

Although twice isn't a pattern just yet, it is strange that both coreutils and bash show this behaviour when running the tests as user nobody.

I've never seen or read about this behaviour before and can only conclude that you must have done something wrong at some point.

Can you post the output of the following (from within the chrooted environment):You mention the same behaviour when doing bash. Can you post the exact error(s) shown?

=====================================================================

root:/# grep nobody /etc/passwd /etc/group
/etc/passwd:nobody:x:99:99:Unprivileged User:/dev/null:/bin/false

=====================================================================

I have no idea what it means can u explain what does it do

That entry looks correct.

This is a passwd entry for a specific user, user nobody in this case.

Have a look her for an explanation of all the used fields: Understanding /etc/passwd File Format


How about my other question?

root:/sources/bash-4.2# su nobody -s /bin/bash -c "PATH=$PATH make tests"

***********************************************************
* *
/bin/sh: /sources/bash-4.2/bashversion: Permission denied
*
* *
***********************************************************

/bin/sh: line 0: cd: ./tests: Not a directory
make: *** [tests] Error 1

It seems user nobody isn't allowed access.

Did you execute the chown -Rv nobody . part (for both coreutils and bash)?

yes I did execute chown for both processes

Don't you mean directories and files? This command recursively changes the owner of all files and directories to nobody. It doesn't concern processes.

Anyway: I'm out of ideas. You must be doing something wrong, but I cannot come up with anything I haven't mentioned before.