| Summary: | sys-devel/gcc: killing USE='build bootstrap' | ||
|---|---|---|---|
| Product: | Gentoo Release Media | Reporter: | SpanKY <vapier> |
| Component: | Stages | Assignee: | Gentoo Release Team <releng> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | toolchain |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
I'll test this change during this weekend and will report back. Jorge said things seemed to work for him http://sources.gentoo.org/eclass/toolchain.eclass?r1=1.567&r2=1.568 The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f210bb3d7324b1a6c1fe9d5e98cdfd57241d6499 commit f210bb3d7324b1a6c1fe9d5e98cdfd57241d6499 Author: Sam James <sam@gentoo.org> AuthorDate: 2024-09-28 23:00:54 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-09-29 00:15:58 +0000 dev-lang/gnat-gpl: rename USE=bootstrap -> USE=system-bootstrap, invert meaning USE=bootstrap has/had a special meaning in <EAPI 5 and it also ends up stable-masked apparently too. It was dropped from use.desc in af748c0468c6ab3ce760de2bfd84f4cef1eb9bcf and dropped from sys-devel/gcc a while ago too (bug #440224). To facilitate automatically using gnat-gpl in sys-devel/gcc, do two things: * Rename USE=bootstrap -> USE=system-bootstrap * Make USE=system-bootstrap mean "I need a working Ada compiler to build this" (i.e. invert its meaning) to match dev-java/openjdk and dev-lang/rust. Bug: https://bugs.gentoo.org/137268 Bug: https://bugs.gentoo.org/440224 Bug: https://bugs.gentoo.org/547358 Bug: https://bugs.gentoo.org/919667 Signed-off-by: Sam James <sam@gentoo.org> dev-lang/gnat-gpl/gnat-gpl-2021-r5.ebuild | 12 ++++++------ dev-lang/gnat-gpl/metadata.xml | 2 +- 2 files changed, 7 insertions(+), 7 deletions(-) |
in the past, these flags did more. today, they do one thing -- force gcc-config to be run. but the current logic should already take care of that. can you try building stages with this change: should_we_gcc_config() { # we always want to run gcc-config if we're bootstrapping, otherwise # we might get stuck with the c-only stage1 compiler - use_if_iuse bootstrap && return 0 - use build && return 0 # if the current config is invalid, we definitely want a new one