Summary: | sys-devel/gcc doesn't build C++ compiler when USE="build" is enabled | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | John W Eckhart <jweckhart> |
Component: | Eclasses | Assignee: | Gentoo Release Team <releng> |
Status: | VERIFIED WONTFIX | ||
Severity: | normal | CC: | toolchain |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | [PATCH] Correct is_cxx to build c++ when USE="build" |
Description
John W Eckhart
2007-03-22 16:58:42 UTC
Created attachment 114068 [details, diff]
[PATCH] Correct is_cxx to build c++ when USE="build"
Comment on attachment 114068 [details, diff]
[PATCH] Correct is_cxx to build c++ when USE="build"
no, either it's "use build && return 1" or it's nothing ... you cant have USE=build force ignore USE=nocxx
let the release team figure out if they want to change the behavior it's always been: stage1: C only (USE=build) stage2: C/C++ (USE=bootstrap) in other words, the current code is correct by design ... you've interpreted the should_we_gcc_config logic incorrectly The reason I encountered this bug was that rsync requires popt, which requires c++. Should I open a new bug against the release team to resolve the C++ dependency? I could barely follow what you said that you've done, but building stages from a 2006.1 seed stage3 requires no modifications to said seed stage. Release Engineering does *not* want the meaning of USE=build to change *at all* and see no "bug" here. If your stages didn't build, it is likel ybecause of an error that you have made, seeing as how I've had 9 architectures build stages for 2007.0 just fine using the latest versions of catalyst and the default settings. I'll move this to the mailing list for now, I must have missed something important. |