1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Peter Simons wrote: |
5 |
| First of all, thanks to all you guys for maintaining the hardened |
6 |
| profile! Consider me a happy user. About two weeks ago, I installed a |
7 |
| Gentoo machine from the scratch with _all_ the nifty features: |
8 |
| hardened-sources with SELinux, PaX, hardened-gcc, super-freeswan ... |
9 |
| everything. And it worked like charm, the whole installation took less |
10 |
| than 6 hours. Honestly, Gentoo rocks. :-) |
11 |
| |
12 |
| I have a question, though: What happens when I update gcc, glibc, or |
13 |
| both? Does this affect hcc in some way? I assume, hcc uses the |
14 |
| versions it has been compiled for and I'd have to un-/install it after |
15 |
| updating gcc, and then after updating glibc again. Or does Portage |
16 |
| handle all this? |
17 |
| |
18 |
| Peter |
19 |
| |
20 |
| |
21 |
| -- |
22 |
| gentoo-hardened@g.o mailing list |
23 |
| |
24 |
The gcc ebuild handles it all :) |
25 |
Basically, it calls hardened-gcc -A after it emerges, reactivating hgcc |
26 |
for the new gcc. |
27 |
|
28 |
Gentoo Hardened takes care of you :) |
29 |
|
30 |
Cheers, |
31 |
//zhen |
32 |
- -- |
33 |
John Davis |
34 |
Gentoo Linux Developer |
35 |
<http://dev.gentoo.org/~zhen> |
36 |
|
37 |
- ---- |
38 |
Knowledge can be more terrible than ignorance if you're powerless to |
39 |
change your world. |
40 |
-----BEGIN PGP SIGNATURE----- |
41 |
Version: GnuPG v1.2.3 (GNU/Linux) |
42 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
43 |
|
44 |
iD8DBQE/jZmsZlASNRlGLUcRAhauAJwIalbfwomOdJ0MlDbp46x/21vM6wCghq7S |
45 |
aRpPaA9Nw3/Nziap5s9uVgw= |
46 |
=/9Ta |
47 |
-----END PGP SIGNATURE----- |
48 |
|
49 |
|
50 |
-- |
51 |
gentoo-hardened@g.o mailing list |