Failed on chapter 6.7.1. Installation of Linux API Headers, make headers_check
 

Hello to all from Siberia!

I am strictrly following the LFS book v7.0.
I have failed on step 6.7.1. "Installation of Linux API Headers" with a message:

root:/sources/linux-3.1# make mrproper
CLEAN include/linux/version.h
root:/sources/linux-3.1# make headers_check
CHK include/linux/version.h
UPD include/linux/version.h
HOSTCC scripts/basic/fixdep
gcc: error trying to exec 'as': execvp: No such file or directory
make[1]: *** [scripts/basic/fixdep] Error 1
make: *** [scripts_basic] Error 2


I found that many people asked for the resolution of this problem but I have not found a solution. There is an advise to execute version-check.sh script from the chapter "vii. Host System Requirements" which checks a host system. I am not sure if the result of the verification should be the same after we change the root (/) directory on step "6.4. Entering the Chroot Environment", but here it is:

root:/# bash version-check.sh
bash, version 4.2.10(1)-release
/bin/sh -> /tools/bin/bash
Binutils: version-check.sh: line 8: ld: command not found
version-check.sh: line 9: bison: command not found
yacc not found
bzip2, Version 1.0.6, 6-Sept-2010.
Coreutils: 8.14
diff (GNU diffutils) 3.2
find (GNU findutils) 4.4.2
GNU Awk 4.0.0
awk not found
gcc (GCC) 4.6.1
version-check.sh: line 22: /lib/libc.so.6: No such file or directory
grep (GNU grep) 2.9
gzip 1.4
Linux version 3.0.0-14-generic (buildd@palmer) (gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) ) #23-Ubuntu SMP Mon Nov 21 20:34:47 UTC 2011
m4 (GNU M4) 1.4.16
GNU Make 3.82
patch 2.6.1
Perl version='5.14.2';
GNU sed version 4.2.1
tar (GNU tar) 1.26
Texinfo: makeinfo (GNU texinfo) 4.13
xz (XZ Utils) 5.0.3
gcc: error trying to exec 'as': execvp: No such file or directory
Compilation failed


I would like to note that the test succeed on the host system:

bash, version 4.2.10(1)-release
/bin/sh -> /bin/dash
Binutils: (GNU Binutils for Ubuntu) 2.21.53.20110810
bison (GNU Bison) 2.4.1
/usr/bin/yacc -> /usr/bin/bison.yacc
bzip2, Version 1.0.5, 10-Dec-2007.
Coreutils: 8.5
diff (GNU diffutils) 3.0
find (GNU findutils) 4.4.2
GNU Awk 3.1.8
/usr/bin/awk -> /usr/bin/gawk
gcc (Ubuntu/Linaro 4.6.1-9ubuntu3) 4.6.1
GNU C Library (Ubuntu EGLIBC 2.13-20ubuntu5) stable release version 2.13
grep (GNU grep) 2.9
gzip 1.3.12
Linux version 3.0.0-14-generic (buildd@palmer) (gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) ) #23-Ubuntu SMP Mon Nov 21 20:34:47 UTC 2011
m4 (GNU M4) 1.4.16
GNU Make 3.81
patch 2.6.1
Perl version='5.12.4';
GNU sed version 4.2.1
tar (GNU tar) 1.25
Texinfo: makeinfo (GNU texinfo) 4.13
xz (XZ Utils) 5.0.0
Compilation OK

There are opinions the test should pass always. So, I decided to find why it does not.

"ld" command cannot be found in the set of directories:
root:/# echo $PATH
/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin

I found that file "ld" is located at "/tools/i686-lfs-linux-gnu/bin/" which is not in the $PATH value. I am sure about the file has been found, but the following comman fails:

root:/# /tools/i686-lfs-linux-gnu/bin/ld --version
bash: /tools/i686-lfs-linux-gnu/bin/ld: No such file or directory


Can anybody clarify the situation, and help me (and us) to pass chapter 6.7.1? :)

Thank you in advance.

Hi

Did you logout /reboot etc before this, if so did you mount the virtual files, Chapter 6.2, before chroot? You should be building on the lfs you have built so far

Yes, it happened I rebooted after I started Chapter 6. I lost $LFS variable and etc. Then I recovered following the advice:
http://www.linuxquestions.org/questi...lation-377597/

I have made corrections in the code suggested there according to the version 7.0. In fact, after rebooting next commands were executed (partition is correct to my system) :

Then, I repeated all the steps of Chapter 6. Commands like "mkdir" and "ln" failed that time for the reason the directories existed already, but I did all the steps to be sure nothing is missing.

You might want to have another look at chapter 5, section 5.2 and make sure your toolchain is correct. In that section there is a highlighted area labeled "important" which contains some tests. One test is to unpack Binutils and run the "./config/guess" script. Have you run that? The next paragraph also points out a "sure-fire" way of determining the name of your dynamic linker. I'm guessing that section 5.2 may help find the problem for you.

Thank you for pointing out this part. No, I did not do it. In the beginning of Chapter "5.2. Toolchain Technical Notes" says that "Most of this information will be clearer after performing an actual build. This section can be referred to at any time during the process". So I counted on the coming sections.

I have done the tests mentioned in the chapter now, and the result is following.
Checking for target platform:
Determining the name of the dynamic linker:
So, everything seems fine.

The following advice from Chapter 5.2 did not have sense to me, because at that point I could not even figure out what a "gcc's specs file" means.
"After the Glibc installation, change gcc's specs file to point to the new dynamic linker in /tools/lib. This last step is vital..."

As I understand, later in the Chapter "5.7. Glibc-2.14.1" the books gives the explicit command to do what was mentioned before:
Are the chapters 5.2 and 5.7 saying the same?

I am wondering about what I should do now. As to me, I have provided all the information which can be used to make a conclusion about the problem. If there is not a clear way to determine a reason of it, can be just a few steps repeated with an additional checking, or I have to start from the very beginning? It would be discouraging...

By the time you get to 6.7.1 "ld" should be in your /tools/bin directory. "ld" is part of the binutils package so again I'm drawn back to chapter 5. Since 5.9 actually builds the binutils I would back up at least to tests in 5.8. If those tests pass then I would re-do 5.9 (the environment will have to be set up for the "lfs" user as stated earlier in chapter 5.) 5.9 will build ld and prepare it for use.

error trying to exec 'as': execvp: No such file or directory
 

I have been working with LFS(v7.0) from the last month and i have struck in this 6.7 installation of Linux api headers and i have been getting the error :

gcc: error trying to exec 'as': execvp: No such file or directory
make[1]: *** [scripts/basic/fixdep] Error 1
make: *** [scripts_basic] Error 2

can anybody help me with this.....

Hi,

Both ld and as are part of binutils. Something must have gone wrong during the install in chapter 5 (or possibly a PATH issue).

The test did not succeed, see the red part. That should read bash, not dash.

Hope this helps.

I had the same. Have started from the beginning
 

Hi kedar kapil!
Chapter 5.2 says that In my installation process I found that the assembler as is missing in /tools/bin location. So I have had to go back, and started from the very beginning.

Probably, you missed an command in one section like I did (no idea where).

Now I use the LFS chapter-by-chapter complete commands from that thread:
http://www.linuxquestions.org/questi...-notes-927674/
It is very helpful.

But be careful! Some versions of tools have been changed in the current version in LFS book! So, you have to verify all the options of .conifg before you execute it.

thanx sunmoon and dauuna....my friend has been stuck with another error in the chroot environment during the installation of linux api headers and the error is as follows:

/bin/sh: perl: command not found
make[2]: *** [/sources/linux-3.1/usr/include/asm-generic/.install] Error 127
make[1]: *** [asm-generic] Error 2
make: *** [headers_install] Error 2


can you suggest me where the error is...by the way he too has got some error while entering the chroot envi and so he reinstalled the complete toolchain carefully...despite doing that he still got the above error......so can you suggest me an answer....

Hi,
As stated by the error: Perl is not (correctly) installed.

Hope this helps.

I started the building process from the beginning of the Chapter 5, and have passed the Chapter 6.7.1 with no errors. The problem is solved then.

So I think I made a mistake in the first pass wich was not found.

Again, I would like to mention that this thread can be usefull http://www.linuxquestions.org/questi...-notes-927674/.

Thanks to everybody who tried to help me.