commit: 5f74f9d9698950a8204c22eddac11eb4654d260e Author: Sam James <sam <AT> gentoo <DOT> org> AuthorDate: Sun Jan 1 22:09:28 2023 +0000 Commit: Sam James <sam <AT> gentoo <DOT> org> CommitDate: Sun Jan 1 22:09:28 2023 +0000 URL: https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=5f74f9d9
2023-01-01-hardening-fortify-assertions: mention 'gcc-config latest' Signed-off-by: Sam James <sam <AT> gentoo.org> .../2023-01-01-hardening-fortify-assertions.en.txt | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/2023-01-01-hardening-fortify-assertions/2023-01-01-hardening-fortify-assertions.en.txt b/2023-01-01-hardening-fortify-assertions/2023-01-01-hardening-fortify-assertions.en.txt index 3b2ff02..ea3ac1b 100644 --- a/2023-01-01-hardening-fortify-assertions/2023-01-01-hardening-fortify-assertions.en.txt +++ b/2023-01-01-hardening-fortify-assertions/2023-01-01-hardening-fortify-assertions.en.txt @@ -39,9 +39,10 @@ of these improvements early, before GCC 12 is marked stable. To fully take advantage of these new settings, GCC must first be upgraded, and then all packages must be re-emerged: -1. emerge --sync -2. emerge --verbose --oneshot ">=sys-devel/gcc-12.2.1_p20221231" -3. emerge --verbose --emptytree @world +1. # emerge --sync +2. # emerge --verbose --oneshot ">=sys-devel/gcc-12.2.1_p20221231" +3. # gcc-config latest +4. # emerge --verbose --emptytree @world ## Troubleshooting
