[gentoo-user] Re: Argh, palemoon again ** 3 [Was: GCC 5.4.0]

[Ian Zimmerman]

On 2017-04-24 11:16, Ian Zimmerman wrote:

> gcc-5_error() {
> 	eerror "You are currently on a gcc 5.* compiler profile."
> 	eerror "Building Pale Moon with gcc >=5 results in a very unstable build."
> 	eerror "You can use gcc-config to change your compiler profile,"
> 	eerror "just remember to change it back afterwards."
> 	eerror "You need to have the appropriate versions of gcc installed"
> 	eerror "for them to be shown in gcc-config."
> }
>
> And sure enough, palemoon is one of the packages revdep-rebuild wants to
> make over.
>
> So - what to do?  I can't live without palemoon now.  Does it make sense
> to exclude it (as in '-- --exclude gcc palemoon') and keep the old gcc
> slot around?  I guess that will work if palemoon is linked with the
> -rpath option.
>
> Or do I have to mask gcc-5 until palemoon is fixed (and will it ever be?)

Well, now I am really confused, and scared :(  Overthinking, right!

I switched gcc-config back to 4.9.4:

root@matica ~ # gcc-config -l
 [1] x86_64-pc-linux-gnu-4.9.4 *
 [2] x86_64-pc-linux-gnu-5.4.0

But:

 [23+0]~$ ldd /usr/bin/palemoon
	linux-vdso.so.1 (0x00007ffd1cb8a000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fd5202a7000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00007fd5200a3000)
	libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/libstdc++.so.6 (0x00007fd51fca5000)
                                                       ^^^^^
    libm.so.6 => /lib64/libm.so.6 (0x00007fd51f9a0000)
	libc.so.6 => /lib64/libc.so.6 (0x00007fd51f602000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fd5204c4000)
	libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/libgcc_s.so.1 (0x00007fd51f3eb000)
                                                      ^^^^^

(And the same for any C++ based binary.)

And it is not just a UI quirk in ldd, I verified by looking at /proc/$PID/maps.

Do I just have to unmerge gcc-5?  What good is the switching gadget then?

-- 
Please *no* private Cc: on mailing lists and newsgroups
Personal signed mail: please _encrypt_ and sign
Don't clear-text sign:
http://primate.net/~itz/blog/the-problem-with-gpg-signatures.html