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

[Ian Zimmerman]

On 2017-04-24 14:44, Mick wrote:

> 1. Emerge the new gcc:
>
> emerge -uaDv gcc
>
> 2. List available gcc versions:
>
> gcc-config -l
> [1] x86_64-pc-linux-gnu-4.9.4 *
> [2] x86_64-pc-linux-gnu-5.4.0
>
> 3. Select the new gcc version:
>
> gcc-config 2
> gcc-config -l
> [1] x86_64-pc-linux-gnu-4.9.4
> [2] x86_64-pc-linux-gnu-5.4.0 *
>
> 4. Source the new profile:
>
> . /etc/profile
>
> 5. Rebuild all packages that have a dependency on libstdc++.so.6':
>
> revdep-rebuild --library 'libstdc++.so.6' -- --exclude gcc
>
> 6. Clean old versions of gcc you no longer need:
>
> emerge --depclean -a -v

And now I know why I was afraid of this.  It was there in the back of my
mind, but stack height was too large.

Quoting palemoon-*.eclass:

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?)

-- 
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