Hi there,

My first problem with the very first package, this doesn't bode well!

When I get to the last make command ' make LDFLAGS="-all-static" ' it bombs out with:

../../binutils-2.15.91.0.2/binutils/bucomm.c:425: warning: the use of `mktemp' is dangerous, better use `mkstemp'
ar.o(.text+0x854): In function `mri_emul':
../../binutils-2.15.91.0.2/binutils/ar.c:148: undefined reference to `yyparse'
collect2: ld returned 1 exit status
make[3]: *** [ar] Error 1
make[3]: Leaving directory `/lfs/tools/binutils-build/binutils'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/lfs/tools/binutils-build/binutils'
make[1]: *** [all-recursive-am] Error 2
make[1]: Leaving directory `/lfs/tools/binutils-build/binutils'
make: *** [all-binutils] Error 2

I'm building it on Suse 9.2 proffesional and have done everything it asked in the previous chapters. My kernel version is 2.6.8-24. Any suggestions on how to make this less painful? Having a problem on the first package doesn't instill me with confidence!

Dave

{EDIT}
I did make install and carried on with gcc installation which worked fine, but I don't want a broken toolchain that bites me when I reach the end, that'd just be a waste!

undefined reference to `yyparse' - this is a flex function. Have you got flex installed?

I installed flex, but haven't been able to check if it works. My root user seems to have problem, I deleted the lfs user and group and the binutils+gcc packages because I wanted to start this thing from scratch. Now when I did an su the root user didn't goto /root. it stayed in my directory. When I typed 'groupadd lfs' it couldn't find the command! I had to do a whereis and type it from the directory.

When I tried to do the configure for binutils it said /bin/sh: Bad interpreter

What have I done?!? I ran Suse system check and it's still broke.

What has lfs (or me) done to the system to do this, and how can I fix it? Besides a full reinstall (not the end of the world, but I don't feel like redoing mplayer, quake3 and Nvidia).

My original user still seems to work fine, I ran a ./configure on mplayer with no issues.

Dave.

The point of creating the user lfs is partly to prevent damage to your host system. A user can't install software system side and so can't do any harm. The user lfs only has write permission in /home/lfs and /mnt/lfs/{sources,tools}
It sounds like you were running things as root. This is unavoidable when you come to chroot into the lfs system. It is not what you should be doing whilst you are compiling on your host system.

I had the same problem on my mdk 10.1 community.
and after installing bison and flex the problem was resolved...

Thanks

Yea, thanks alot for the help on this issue, the Book should really warn about needing bison and flex (I have no idea what they are used for ...?)
I didn't realize that I also needed to delete the current make files and redo the configurations.
Wow what work , I hope its worth it though!