aha, once again,
dev@dev-VirtualBox /mnt/erraticOS/usr/src/gcc-build $ gcc --version gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3 Copyright (C) 2011 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. dev@dev-VirtualBox /mnt/erraticOS/usr/src/gcc-build $ apt-get I knew I figured this out once before, and the reason I knew is because I removed the -fbuilding-libgcc (just now and before) from the makefile and came to this problem) cc1plus: error: unrecognized command line option ‘-std=gnu++11’ which has to do with the fact that cc1plus 4.6 doesn't have support for that ;) odd that they didn't include the build process for compiling 4.7 from 4.6 huh? simple symlink (after installing the gcc.47 ppa fixes it....because in the beginning god crapped out a gcc 4.7 for everyone to compile the new gcc 4.7 that they wrote with.) It'd totally be legit if it was because you need gcc 4.7 (not g++ 4.7) to compile g++ 4.7 but its totally not that way apparently. I was really disappointed to find this... pisses me off I kinda have lost a little faith in this but then again, I don't really have much anyway considering the circumstances. NOW to figure out why previously the > #make -C ld clean > #make -C ld LIB_PATH=/usr/lib:/lib was causing segfault, and also why I have to specify --host=x86_64-linux-gnu because for whatever reason config.guess doesn't work on the second pass of binutils. then I guess once I have everything else built I should be able to chroot into it in theory but we'll see, I have a feeling its going to be a huge waste of time. On Nov 14, 2012, at 6:49 AM, Paige Thompson <erra...@devel.ws> wrote: > failfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfail > > make[2]: Entering directory > `/mnt/erraticOS/usr/src/gcc-build/x86_64-linux-gnu/libgcc' > # If this is the top-level multilib, build all the other > # multilibs. > 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[2]: *** [_muldi3.o] Error 1 > make[2]: Leaving directory > `/mnt/erraticOS/usr/src/gcc-build/x86_64-linux-gnu/libgcc' > make[1]: *** [all-target-libgcc] Error 2 > make[1]: Leaving directory `/mnt/erraticOS/usr/src/gcc-build' > make: *** [all] Error 2 > compile failed in /mnt/erraticOS/usr/src/gcc-build > > failfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfailfail > > > 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: > https://github.com/paigeadele/erraticOS/blob/master/usr/src/bootstrap_userland.sh > > 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. > > thanks. > >
-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
