| 1 |
Am Montag, 4. Dezember 2017, 03:58:40 CET schrieb tuxic@××××××.de: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> what could fail, when doing the change to PIE-enabled applications |
| 5 |
> on base of the regular updates? |
| 6 |
> Compilation may fail, if libs are included and not flagged as to be |
| 7 |
> recompiled, which are of the "old standard"... |
| 8 |
> What else can fail? What may be the worst scenario? |
| 9 |
|
| 10 |
The worst case scenario is that you spend too much time worrying about it. |
| 11 |
|
| 12 |
Some devs including me switched profile without rebuilding anything outside |
| 13 |
the normal updates. (Because the guidelines were not written up yet.) |
| 14 |
Things just kept working fine. |
| 15 |
|
| 16 |
What can go wrong is that you get random build failures at some point later |
| 17 |
(likely with a linker message about failed relocations). These indicate that |
| 18 |
the linker was instructed to combine PIE and non-PIE code, which doesnt work. |
| 19 |
So one of the involved packages has not been rebuilt yet and needs to be |
| 20 |
rebuilt. This is mostly happening when static libraries are involved. |
| 21 |
|
| 22 |
-- |
| 23 |
Andreas K. Hüttel |
| 24 |
dilfridge@g.o |
| 25 |
Gentoo Linux developer |
| 26 |
(council, toolchain, perl, libreoffice, comrel) |
Archives