On Wed, Jan 24, 2018 at 11:43:31AM +0000, Peter Humphrey wrote > On Tuesday, 23 January 2018 18:27:21 GMT Walter Dnes wrote: > > Yes, I do have them both installed already. > > > Is this the official Pale Moon, or an unofficial build? > > It's www-client/palemoon-bin-27.7.1::palemoon. I don't know whether > that's "official", because when I "layman -a palemoon" I'm told it's > not an official overlay. Different officialdoms, I suppose.
Disclosure... I'm a volunteer for the Pale Moon project (not an official spokesman). I do a contributed build for Pentium3-class machines. My idea of "official" is obviously "from the Pale Moon website". Can you do a quick-n-dirty install from the official tarball to check if the icon problem happens with the official Pale Moon? This test will install into $HOME/pm 1) Go to http://linux.palemoon.org/download/mainline/ and download the appropriate (32 or 64 bit) tarball for your system. 2) killall palemoon # Ignore error message if Pale Moon not running. 3) rm -rf $HOME/pm && mkdir $HOME/pm # Start from a known state 4) tar -C $HOME/pm -xvjf <tarball_name> # Extract tarball 5) $HOME/pm/palemoon/palemoon # Launch Pale Moon Note; this install is self-contained. It does not splatter stuff all over various library directories. Does the icon problem still happen with the official tarball? > This is with gcc 4.9.4, and I get the same with gcc 6.4.0. I've only just > noticed that about -fPIC; haven't all those problems been fixed by now? 6.3.0 builds Pale Moon OK on profile 13. I'll soon be doing the switch over to 17 on my 32-bit desktop. You might be able to get things working with custom flags for the Pale Moon ebuild using package.env as per... https://wiki.gentoo.org/wiki//etc/portage/package.env -- Walter Dnes <[email protected]> I don't run "desktop environments"; I run useful applications
