> With --disable-libstdcxx you can't bootstrap gcc, because stage 2 gcc has to
> link to stage 1 libstdc++.
Including libstdcxx in the configure did the trick. Thanks for your help!
> Right. If you just want to build the compiler front-ends without the
> runtime libs then don't try to do a 3-stage bootstrap, just configure
> then run 'make all-gcc' to build just the stage1 compilers, and then
> 'make install-gcc'.
I'd prefer the bootstrap, to verify the compiler can build itself..
> Maybe it would help if you explain what you're trying to achieve with
> this configure command.
My goal is to create a minimal C/C++ compiler that I can use to jump-start a blank GNU environment from source. Think of an alternative to LFS. (I tried LFS, and failed apocalyptic ally.) The bootstrap is sort of a safety feature (although not the only one) to remove any attachment from the host gcc.
Hope my approach makes sense: Just build and install to something that will become /usr/bin/{cc,c++,gcc,g++} once chroot'ed? Is libgcc needed for gcc to run, or is it just needed when developing against it?
Regards,
Winston
