> Unless you are crazy enough to have USE=nocxx, you get a c++ compiler > with gcc. Others are controlled by USE flags.
I don't believe that I included the USE=nocxx variable. I will give another try at re-building GCC a little later just to see if I get the same effect. (Honestly, I did add a few additional Use Flags before I emerge gcc. gdj and fortran were some of them. I went through and pruned a few of them when I first started having problems with some of packages failing to emerge.) > > gcj - java compiler > fortran - fortran compiler > ...and so on. > > > ncurces, groff, sys-libs/db, python > > > > All fail with the same error > > What error? These various errors sound very similar. Here is an error I've transposed from the last package in the emerge --resume --skipfirst. ../../build-aux/depcomp:line 512: execg++ not found make[4]: *** [calc++-scanner.o] Error 127 Other packages will give up during the sanity check when they discovered there wasn't a g++ compiler for available. Thanks for the reply. Regards, Richard Broersma Jr. -- [email protected] mailing list
