| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 14/11/14 10:50 AM, Andreas K. Huettel wrote: |
| 5 |
> Am Freitag, 14. November 2014, 15:49:17 schrieb Andrew Savchenko: |
| 6 |
>> Hi, |
| 7 |
>> |
| 8 |
>> On Fri, 14 Nov 2014 09:08:17 -0500 Michael Orlitzky wrote: |
| 9 |
> |
| 10 |
>>> |
| 11 |
>>> Question 1: is it desirable to e.g. switch compilers, compile |
| 12 |
>>> systemd, and then switch back? |
| 13 |
>> |
| 14 |
>> This is definitely a good idea. Some packages are picky about |
| 15 |
>> gcc versions, e.g. dev-util/nvidia-cuda-toolkit usually lags |
| 16 |
>> behind the latest available gcc version by one. |
| 17 |
> |
| 18 |
> E.g. cmake may fail to run correctly if it is built with a newer |
| 19 |
> compiler than the one currently selected. Or so I remember from a |
| 20 |
> bug some time ago. |
| 21 |
> |
| 22 |
> This is a recipe for major trouble. |
| 23 |
> |
| 24 |
> |
| 25 |
|
| 26 |
It used to be that after a gcc upgrade people were expected to 'emerge |
| 27 |
- -e @world' to make sure everything would work properly by being |
| 28 |
rebuilt for the new version. It's always a possibility that we need |
| 29 |
to go back to that type of policy for a particular subset of the tree. |
| 30 |
|
| 31 |
|
| 32 |
-----BEGIN PGP SIGNATURE----- |
| 33 |
Version: GnuPG v2 |
| 34 |
|
| 35 |
iF4EAREIAAYFAlRmO2IACgkQ2ugaI38ACPBueAD/StqbdxmsPwbDmSgczVGwLThj |
| 36 |
mISg96OlEm8TktUONP4A/AnJm0cV7+APPM97YbCg24qC+7Hz4JtSBZnkEUMDghHS |
| 37 |
=GfSI |
| 38 |
-----END PGP SIGNATURE----- |
Archives