| 1 |
> so I'm still on 4.7.3; but if I set 4.8.3 |
| 2 |
> as the default, should I rebuild @system ? |
| 3 |
> |
| 4 |
> # gcc-config -l |
| 5 |
> [1] x86_64-pc-linux-gnu-4.7.3 * |
| 6 |
> [2] x86_64-pc-linux-gnu-4.8.3 |
| 7 |
> |
| 8 |
> |
| 9 |
> I saw the news item about 4.8.3-SSP, which I think is a good idea, but |
| 10 |
> how deeply, if at all, do I need to rebuild packages ? |
| 11 |
> Is there any special steps I should take now in prepartion for 4.9.x? |
| 12 |
> caveats? |
| 13 |
> |
| 14 |
> @system ? |
| 15 |
> @world ? |
| 16 |
> a specific list of packages only ? |
| 17 |
|
| 18 |
Based on my experience going from 4.7 to 4.8 was seamless, you can |
| 19 |
choose to not rebuild anything if you'd like. If you want to start |
| 20 |
taking advantage of -fstack-protector by default you can rebuild |
| 21 |
whatever you'd like, although if you're paranoid about security you |
| 22 |
should rebuild everything, ie. @system @world to make sure all your |
| 23 |
binaries and the libraries they dynamically load have the stack |
| 24 |
smashing guard built in. |
| 25 |
|
| 26 |
Going to 4.9 though is another thing. Apparently they broke the ABI for |
| 27 |
the standard C++ library, so once you start compiling C++ stuff with |
| 28 |
4.9 you better go all in (I did @system @world with 4.9 and had very |
| 29 |
few things that failed to compile[1], it's looking pretty good already). |
| 30 |
|
| 31 |
--Mark |
| 32 |
|
| 33 |
[1] https://bugs.gentoo.org/show_bug.cgi?id=526140 |
Archives