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