The 'unstable' version of gettext will not build from a stage1 system, users wanting a 'pure' unstable system have to totally mask gettext-0.12 and gettext-0.12.1. I understand that this is what the 'unstable' users should expect, but this will eventually need fixing. Reproducible: Always Steps to Reproduce: 1. Set up stage1 system as per install documentation. 2. Add KEYWORDS="~x86" to make.conf 3. Run build/bootstrap.sh Actual Results: checking for i686-pc-linux-gnu-g++... g++ checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking dependency style of g++... none checking how to run the C++ preprocessor... /lib/cpp configure: error: C++ preprocessor "/lib/cpp" fails sanity check See `config.log' for more details. configure: error: /bin/sh './configure' failed for autoconf-lib-link !!! ERROR: sys-devel/gettext-0.12.1 failed. !!! Function econf, Line 324, Exitcode 1 !!! econf failed Expected Results: System emerges to stage2 state, with gettext-0.12.1 I've seen this report failure at "Function econf, Line 324, Exitcode 1" and "Function econf, Line 321, Exitcode 1"
It looks like gettext-0.12 needs a c++ compiler, which isn't supplied with the current stage1 tarballs. The options are (if you want to do it yourself) to build your own stage1, or to do a stable bootstrap.sh followed by an unstable bootstrap.sh (I'm testing if this works now).
I've already done the stable bootstrap/unstable and it works just dandy. Could I remedy this by changing the gcc ebuild to add language c++ under -build -bootstrap flags? Eventually I'd imagine that Gentoo will switch over to gettext-0.12.* and this has to get fixed before that, right?
Just found the part of gcc-3.3.1-r1.ebuild that defines what flags define languages, added c++ to 'build' builds. testing... (thank heavens for fast computers, eh?)
I'm pretty certain that what will happen is that the gcc in the stageball will include c++ support.
*** This bug has been marked as a duplicate of 25080 ***
