1 |
Andreas K. Huettel posted on Mon, 09 Oct 2017 22:58:22 +0200 as excerpted: |
2 |
|
3 |
> Please consider switching from your current 13.0 profile to the |
4 |
> corresponding 17.0 profile soon after GCC-6.4.0 has been stabilized on |
5 |
> your architecture. The 13.0 profiles will be deprecated and removed in |
6 |
> the near future. |
7 |
> |
8 |
> Switching involves the following steps: |
9 |
> If not already done, |
10 |
> * Use gcc-config to select gcc-6.4.0 or later as system compiler |
11 |
> * Re-source /etc/profile: |
12 |
> . /etc/profile |
13 |
> * Re-emerge libtool Then, |
14 |
> * Select the new profile with eselect |
15 |
> * Re-emerge, in this sequence, gcc, binutils, and glibc |
16 |
> emerge -1 sys-devel/gcc:6.4.0 |
17 |
> emerge -1 sys-devel/binutils |
18 |
> emerge -1 sys-libs/glibc |
19 |
> * Rebuild your entire system |
20 |
> emerge -e world |
21 |
> |
22 |
> If you do not follow these steps you may get spurious build failures |
23 |
> when the linker tries unsuccessfully to combine non-PIE and PIE code. |
24 |
|
25 |
One thing isn't clear here. Is this sequence necessary due to the |
26 |
profile switch itself, because the /profile/ enables PIE by default, or |
27 |
is it gcc-6.4+ that enables PIE, and the profile simply forces the PIE |
28 |
default by forcing gcc-6.4+? |
29 |
|
30 |
The answer makes a big difference to those already on gcc-6.4+ and who |
31 |
presumably already did an empty-tree rebuild of @world when upgrading to |
32 |
it, but not yet on the new profile. Do they have to do all that again |
33 |
when they switch profiles, or is that a bridge they've already crossed |
34 |
with the gcc upgrade? |
35 |
|
36 |
Either way, making the answer to that explicit should be useful, avoiding |
37 |
either an unnecessary full rebuild, or avoiding the problems because the |
38 |
news item wasn't clear and people already on gcc-6.4+ thought the |
39 |
procedure didn't apply to them. |
40 |
|
41 |
-- |
42 |
Duncan - List replies preferred. No HTML msgs. |
43 |
"Every nonfree program has a lord, a master -- |
44 |
and if you use the program, he is your master." Richard Stallman |