Summary: | Unstable build from stage1 fails at gettext-0.12.1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marc Doughty <mdoughty> |
Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED DUPLICATE | ||
Severity: | minor | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Marc Doughty
2003-09-10 17:44:38 UTC
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. |