| 1 |
On Mon, Apr 24, 2017 at 9:53 PM, Ian Zimmerman <itz@×××××××.net> wrote: |
| 2 |
> On 2017-04-24 11:16, Ian Zimmerman wrote: |
| 3 |
> |
| 4 |
>> gcc-5_error() { |
| 5 |
>> eerror "You are currently on a gcc 5.* compiler profile." |
| 6 |
>> eerror "Building Pale Moon with gcc >=5 results in a very unstable build." |
| 7 |
>> eerror "You can use gcc-config to change your compiler profile," |
| 8 |
>> eerror "just remember to change it back afterwards." |
| 9 |
>> eerror "You need to have the appropriate versions of gcc installed" |
| 10 |
>> eerror "for them to be shown in gcc-config." |
| 11 |
>> } |
| 12 |
>> |
| 13 |
>> And sure enough, palemoon is one of the packages revdep-rebuild wants to |
| 14 |
>> make over. |
| 15 |
>> |
| 16 |
>> So - what to do? I can't live without palemoon now. Does it make sense |
| 17 |
>> to exclude it (as in '-- --exclude gcc palemoon') and keep the old gcc |
| 18 |
>> slot around? I guess that will work if palemoon is linked with the |
| 19 |
>> -rpath option. |
| 20 |
>> |
| 21 |
>> Or do I have to mask gcc-5 until palemoon is fixed (and will it ever be?) |
| 22 |
> |
| 23 |
> Well, now I am really confused, and scared :( Overthinking, right! |
| 24 |
> |
| 25 |
> I switched gcc-config back to 4.9.4: |
| 26 |
> |
| 27 |
> root@matica ~ # gcc-config -l |
| 28 |
> [1] x86_64-pc-linux-gnu-4.9.4 * |
| 29 |
> [2] x86_64-pc-linux-gnu-5.4.0 |
| 30 |
> |
| 31 |
> But: |
| 32 |
> |
| 33 |
> [23+0]~$ ldd /usr/bin/palemoon |
| 34 |
> linux-vdso.so.1 (0x00007ffd1cb8a000) |
| 35 |
> libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fd5202a7000) |
| 36 |
> libdl.so.2 => /lib64/libdl.so.2 (0x00007fd5200a3000) |
| 37 |
> libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/libstdc++.so.6 (0x00007fd51fca5000) |
| 38 |
> ^^^^^ |
| 39 |
> libm.so.6 => /lib64/libm.so.6 (0x00007fd51f9a0000) |
| 40 |
> libc.so.6 => /lib64/libc.so.6 (0x00007fd51f602000) |
| 41 |
> /lib64/ld-linux-x86-64.so.2 (0x00007fd5204c4000) |
| 42 |
> libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/libgcc_s.so.1 (0x00007fd51f3eb000) |
| 43 |
> ^^^^^ |
| 44 |
> |
| 45 |
> (And the same for any C++ based binary.) |
| 46 |
> |
| 47 |
> And it is not just a UI quirk in ldd, I verified by looking at /proc/$PID/maps. |
| 48 |
> |
| 49 |
> Do I just have to unmerge gcc-5? What good is the switching gadget then? |
| 50 |
> |
| 51 |
> -- |
| 52 |
> Please *no* private Cc: on mailing lists and newsgroups |
| 53 |
> Personal signed mail: please _encrypt_ and sign |
| 54 |
> Don't clear-text sign: |
| 55 |
> http://primate.net/~itz/blog/the-problem-with-gpg-signatures.html |
| 56 |
> |
| 57 |
|
| 58 |
You did remember to run: |
| 59 |
env-update && source /etc/profile |
| 60 |
|
| 61 |
After doing: |
| 62 |
gcc-config 1 |
| 63 |
|
| 64 |
Did you? |
Archives