[Newbie, LFS-6.5]: Problems with binutils-Pass2 compilation..

Abhinav Chaturvedi achaturvedi at gmail.com
Thu Dec 17 01:32:01 PST 2009


Hi all,
This is my first time compiling Linux kernel and I have run into a problems
in Section 5.9 (binutils-2.19.1 - Pass 2) of LFS-6.5.

Below is my setup information
1. LFS - Version 6.5
2. Distro: OpenSuse - 11.1
3. version-check.sh output
----------------------------------------
bash, version 3.2.39(1)-release
/bin/sh -> /bin/bash
/bin/sh -> /bin/bash
bison (GNU Bison) 2.3
/usr/bin/yacc -> /usr/bin/yacc
Coreutils:  6.12
diff (GNU diffutils) 2.8.7-cvs
find (GNU findutils) 4.4.0
GNU Awk 3.1.6
/usr/bin/awk -> /bin/gawk
gcc (SUSE Linux) 4.3.2 [gcc-4_3-branch revision 141291]
GNU C Library stable release version 2.9
GNU grep 2.5.2
gzip 1.3.12
Linux version 2.6.27.7-9-pae (geeko at buildhost) (gcc version 4.3.2
[gcc-4_3-branch revision 141291] (SUSE Linux) ) #1 SMP 2008-12-04 18:10:04
+0100
m4 (GNU M4) 1.4.12
GNU Make 3.81
patch 2.5.9
Perl version='5.10.0';
GNU sed version 4.1.5
tar (GNU tar) 1.20
makeinfo (GNU texinfo) 4.12
Compilation OK

4. Problem encountered in Section - 5.9.1
5. Error message on 'make' command
---------------------------------------------------------
    checking for string.h... (cached)
no
checking for strings.h... (cached)
no
checking for stdlib.h... (cached)
no
checking time.h usability...
no
checking time.h presence...
no
checking for time.h...
no
checking for unistd.h... (cached)
no
checking fcntl.h usability...
no
checking fcntl.h presence...
no
checking for fcntl.h...
no
checking sys/file.h usability... no
checking sys/file.h presence... no
checking for sys/file.h... no
checking sys/time.h usability... no
checking sys/time.h presence... no
checking for sys/time.h... no
looking for a compliant stdint.h in stdint.h, checking for uintmax_t... no
looking for a compliant stdint.h in inttypes.h, checking for uintmax_t... no
looking for a compliant stdint.h in sys/inttypes.h, checking for
uintmax_t... no
looking for an incomplete stdint.h in stdint.h, checking for uint32_t... no
looking for an incomplete stdint.h in inttypes.h, checking for uint32_t...
no
looking for an incomplete stdint.h in sys/inttypes.h, checking for
uint32_t... no
looking for u_intXX_t types in sys/types.h, checking for u_int32_t... no
looking for u_intXX_t types in inttypes.h, checking for u_int32_t... no
looking for u_intXX_t types in sys/inttypes.h, checking for u_int32_t... no
checking what to include in bfd_stdint.h... stddef.h (using manual
detection)
checking for void *... (cached) no
checking size of void *... (cached) 0
checking for long... (cached) no
checking size of long... (cached) 0
checking for int... no
checking size of int... 0
checking for short... no
checking size of short... 0
checking for char... no
checking size of char... 0
checking for type equivalent to int8_t... configure: error: no 8-bit type
/mnt/lfs/sources/binutils-2.19.1/bfd/configure: line 15985: exit: please:
numeric argument required
/mnt/lfs/sources/binutils-2.19.1/bfd/configure: line 15985: exit: please:
numeric argument required
make[1]: *** [configure-bfd] Error 1
make[1]: Leaving directory `/mnt/lfs/sources/binutils-build2'
make: *** [all] Error 2


6. Any deviations from the document?
--------------------------------------------------------
    As far as I remember, I have stuck to the text. However, I did create a
separate build folder for Pass 2 called binutils-build2. I assumed that the
build folder created in Pass 1 needed to be separate from that in Pass 2.

Other Notes
-------------------
1. The sanity check immediately before 5.9.1 where a dummy.c is created and
compiled using $LFS_TGT-gcc gives the following (correct) output:
           [Requesting program interpreter: /tools/lib/ld-linux.so.2]

I realize that something has gone amiss in previous stages. Could someone
please tell me whether I need to start from scratch or just redo some stage?


Thanks
Abhinav.

-- 
It's the peoples' will, I am their leader, I must follow them. (Jim Hacker
in Yes Minister)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfromscratch.org/pipermail/lfs-support/attachments/20091217/1b4051c6/attachment.html>


More information about the lfs-support mailing list