[lfs-support] gcc 4.7.1 second pass
erratic at devel.ws
Wed Nov 14 06:49:34 PST 2012
make: Entering directory `/mnt/erraticOS/usr/src/gcc-build/x86_64-linux-gnu/libgcc'
# If this is the top-level multilib, build all the other
DEFINES='' HEADERS='../../../gcc/libgcc/config/i386/value-unwind.h' \
../../../gcc/libgcc/mkheader.sh > tmp-libgcc_tm.h
/bin/bash ../../../gcc/libgcc/../move-if-change tmp-libgcc_tm.h libgcc_tm.h
echo timestamp > libgcc_tm.stamp
cc -g -O2 -O2 -g -O2 -DIN_GCC -fomit-frame-pointer -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -fpic -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -fpic -I. -I. -I../.././gcc -I../../../gcc/libgcc -I../../../gcc/libgcc/. -I../../../gcc/libgcc/../gcc -I../../../gcc/libgcc/../include -I../../../gcc/libgcc/config/libbid -DENABLE_DECIMAL_BID_FORMAT -DHAVE_CC_TLS -DUSE_TLS -o _muldi3.o -MT _muldi3.o -MD -MP -MF _muldi3.dep -DL_muldi3 -c ../../../gcc/libgcc/libgcc2.c -fvisibility=hidden -DHIDE_EXPORTS
cc1: error: unrecognized command line option ‘-fbuilding-libgcc’
make: *** [_muldi3.o] Error 1
make: Leaving directory `/mnt/erraticOS/usr/src/gcc-build/x86_64-linux-gnu/libgcc'
make: *** [all-target-libgcc] Error 2
make: Leaving directory `/mnt/erraticOS/usr/src/gcc-build'
make: *** [all] Error 2
compile failed in /mnt/erraticOS/usr/src/gcc-build
when I built the second pass of binutils, this broke too:
#make -C ld clean
#make -C ld LIB_PATH=/usr/lib:/lib
kept saying as segmentation fault something ernother
heres that there script i been usin:
ps I want to gently shove my mac pro out of the window behind my desk so it can fall several stories and explode and make some kid cry because of this, I hope it makes you want to cry too knowing that my preference to windows is much stronger now that I know that regardless of the fact that I have the source, I still can't build it... what makes me even more sad is that LFS is the only resource I can find on the internet for how to do this. How do the ubuttnut and debian people do it.. how does the slackware guy do it... hell the how the hell does gentoo do it I guess I'll take a look... any advice is welcome I would really appreciate the help because i know getting past this toolchain is the hard part and it'll be leaps and bounds better in the chroot.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lfs-support