Hi, emerge groff in the stage1 fails due to non-working c++. [...] checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking that C++ compiler can compile simple program... no configure: error: a working C++ compiler is required !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile, Line 1, Exitcode 1 !!! (no error message) !!! emerge aborting on /usr/portage/sys-apps/groff/groff-1.17.2-r1.ebuild .
EUhm.. any ideas somebody?
close won't fix, groff needs to be built after the second build of gcc.
I can verify this but, not during stage 1, but on a re-merge of groff on a system that is completely up to date with rsync as of July 16th 11am... thought it might be ccache or colorgcc as the problem but not so. Can't seem to figure what is going on here. dave
Groff 1.16.1-r1 does not fail on this dependancy and builds fine... while 1.17 does... should 1.17 be masked untill this is resolved? i am using 2.95.3-r7 dave
with gcc3.2pre configure: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used. checking for i686-pc-linux-gnu-gcc... gcc checking for C compiler default output... configure: error: C compiler cannot create executables !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile, Line 7, Exitcode 77 !!! (no error message) ... now isn't that special :-\ the groff that I have installed, of course, is broken (I see this when I try to open a man page) groff: error while loading shared libraries: libstdc++.so.4: cannot open shared object file: No such file or directory
hm running "/usr/portage/scripts/bootstrap.sh" fixed this problem nm :-)
I assume this is fixed? Long time since i heard anything about it... Closing
