On Wed, 2013-01-16 at 00:00 -0700, [email protected] wrote:
Bruce, Thanks, this resolved the problem. > > Bruce, > > > > Thanks for getting back with me. > > > > I have been able to get the gcc-4.7.1 pass 1 to run to completion; > > however, I have some concerns as to its validity, given what I had to > > do. Let me explain: > > > > After linking /bin/sh -> /bin/bash; installing bison and gawk; > > validating that /usr/bin/yacc -> /usr/bin/bison.yacc, and > > that /usr/bin/awk -> /usr/bin/gawk, I re-configured and ran make again > > in the gcc-build directory. The compilation stilled failed while > > building gcc/c-family/c-cppbuiltin.c; with the same error - > > GNU_USER_TARGET_OS_CPP_BUILTINS() undefined. > > We recommend you remove the source directory, and in this case > gcc-build, and start the section fresh. It appears you started from the > failed position and that results in an undetermined state. > > > I rechecked the instructions and the host requirements; however, it > > appears that the guidelines are being following. > > > > I located the macro definition for GNU_USER_TARGET_OS_CPP_BUILTINS() in > > gcc-4.7.1/gcc/config/gnu.h header and added it to c-cppbuiltins.c. > > > > The compilation then error when compiling gcc/gcc.c. with > > GNU_USER_DYNAMIC_LINKER and GNU_USER_LINKER_EMULATION as undefined. > > > > I located these #define in gcc-4.7.1/gcc/config/i386/gnu.h and added > > this header to gcc.c. > > This should not be necessary. All the instructions needed are in the book. > > > My question is whether this pass 1 build is valid? It seems that my > > having to add headers to .c file is some what unorthodoxy, and could > > result in a bad build. I'm a little reluctant to go forward without some > > feedback. I would have assumed that these defines would have been > > included in some "common" directory path search or not needed for > > compiling gcc-4.7.1 pass 1. > > See above. > > -- Bruce -- gmoore -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
