Hi All,
I am having issues building gcc pass 1 while following the lfs book. this is the error I get:
{code}
-fexceptions -fnon-call-exceptions -fvisibility=hidden -DHIDE_EXPORTS
/mnt/lfs/sources/gcc-build/./gcc/xgcc -B/mnt/lfs/sources/gcc-build/./gcc/ -B/tools/i686-lfs-linux-gnu/bin/ -B/tools/i686-lfs-linux-gnu/lib/ -isystem /tools/i686-lfs-linux-gnu/include -isystem /tools/i686-lfs-linux-gnu/sys-include -g -O2 -O2 -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -fpic -mlong-double-80 -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -Dinhibit_libc -fpic -mlong-double-80 -I. -I. -I../.././gcc -I../../../gcc-4.8.1/libgcc -I../../../gcc-4.8.1/libgcc/. -I../../../gcc-4.8.1/libgcc/../gcc -I../../../gcc-4.8.1/libgcc/../include -I../../../gcc-4.8.1/libgcc/../libdecnumber/no -I../../../gcc-4.8.1/libgcc/../libdecnumber -DHAVE_CC_TLS -DUSE_TLS -o _udivmoddi4.o -MT _udivmoddi4.o -MD -MP -MF _udivmoddi4.dep -DL_udivmoddi4 -c ../../../gcc-4.8.1/libgcc/libgcc2.c \
-fexceptions -fnon-call-exceptions -fvisibility=hidden -DHIDE_EXPORTS
/mnt/lfs/sources/gcc-build/./gcc/xgcc -B/mnt/lfs/sources/gcc-build/./gcc/ -B/tools/i686-lfs-linux-gnu/bin/ -B/tools/i686-lfs-linux-gnu/lib/ -isystem /tools/i686-lfs-linux-gnu/include -isystem /tools/i686-lfs-linux-gnu/sys-include -g -O2 -O2 -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -fpic -mlong-double-80 -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -Dinhibit_libc -fpic -mlong-double-80 -I. -I. -I../.././gcc -I../../../gcc-4.8.1/libgcc -I../../../gcc-4.8.1/libgcc/. -I../../../gcc-4.8.1/libgcc/../gcc -I../../../gcc-4.8.1/libgcc/../include -I../../../gcc-4.8.1/libgcc/../libdecnumber/no -I../../../gcc-4.8.1/libgcc/../libdecnumber -DHAVE_CC_TLS -DUSE_TLS -o decContext.o -MT decContext.o -MD -MP -MF decContext.dep -c ../../../gcc-4.8.1/libgcc/../libdecnumber/decContext.c
../../../gcc-4.8.1/libgcc/../libdecnumber/decContext.c:33:43: fatal error: string.h: No such file or directory
#include <string.h> /* for strcmp */
^
compilation terminated.
make[2]: *** [decContext.o] Error 1
make[2]: Leaving directory `/mnt/lfs/sources/gcc-build/i686-lfs-linux-gnu/libgcc'
make[1]: *** [all-target-libgcc] Error 2
make[1]: Leaving directory `/mnt/lfs/sources/gcc-build'
make: *** [all] Error 2

{code}

The lfs book version is 7.4. My host system is Linux Mint Release 15.
Before this problem I faced build issues with binutils-2.23.2 also, but I did not record the error. Googling around a bit gave me a hint to user MAKEINFO=true option with make, and it worked.

Back to the gcc build issue. I tried the build multiple times and did a make clean between attempts. The configure command I copied directly from the book after trying to build after typing it all by hand.
Please, please help me with this. If there is any other info that I must provide, please let me know.

Thanks in advance!
Aashish

You need to forget about the gcc issue and go back to binutils.

All the commands needed are in the book and there is no need to add or subtract any commands. If you do encounter an error then the chances are that you did something wrong (unless it is mentioned in the book or the errata).

If you "fix" a problem by doing extra stuff not mentioned in the book then the chances are that it will come around and bite you later on.

Hi Drruna,
I agree that the book should be having all commands 'exactly' the way it is meant to be. It was all fine until I ran into the binutils issue. I have checked and rechecked, but I haven't been able to spot a mistake until that step. As per the LFS website there is no errata for the latest (7.4) book.
The workaround that I mentioned, I found it here:
https://lists.gnu.org/archive/html/b.../msg00025.html

Please take a look.
I'm now trying to run configure and make again for binutils. Will update soon.
Appreciate your help! :-)
Aashish

To be honest, there's no point in looking at the solution you found. LFS works without having to do extra stuff that isn't in the book. There also hasn't been any mention of problems with binutils on the LFS mailing list.

Are you 100% sure that your host is compliant? Post the output of the version-check.sh script so we can have a look.

Also: Without any indication what went wrong with binutils we aren't able to help. Post the error shown (including +/- 10 lines leading up to the error).

I went back to building binutils first, and for some reason it worked just fine with make and make install. It must have been something I missed the first time around.

My host is Mint Linux which is forked out of Ubuntu, so I'm guessing it should work just fine. I'm really not sure what I'm missing here: I've been following the book to the very letter. No deviations at all.
Attaching outputs of version-check and configure of gcc-4.8.1.

Thanks!

Attached Files

	version-check-out.txt (785 Bytes, 20 views)
	configure_out.txt (4.5 KB, 16 views)

Its not entirely clear to me what you did or did not do: After successfully building Binutils-2.23.2 - Pass 1, did you remove the gcc and gcc-build directory before retrying GCC-4.8.1 - Pass 1 (as mentioned here: General Compilation Instructions)?

The gcc configure output you attached doesn't show any errors and in your first post you seem to have posted the output of the make command.

Sorry for all that confusion. Let me explain:
The make output in the first post shows the error that I got during gcc build. The build failed after running for a long time (not 5-10 mins). Outputs of version-check script and gcc configure were attached in my previous post. As you mentioned, there seems to be nothing wrong with gcc configure.

By my previous post I had gone back to binutils-build, did a make clean, configure, and then make and make install. As I said, it worked this time. But even after that the gcc build had failed with the same error.

As of writing this post I have deleted my gcc and gcc-build directories (to start over with gcc). I then extracted gcc from the tarball and then followed all the steps exactly as mentioned in the book (including making a new gcc-build directory, etc). I have started a new gcc build, which is in progress. Will post and update on that soon.

Thanks for your time!
Aashish.

It worked this time. I'm pretty sure I didn't do anything different from the last time when I started from scratch. Still, having said that, I'll be even more careful now to follow the book exactly.
Thanks for the prompt response! :-)
Aashish