| 1 |
On Wednesday, 24 January 2018 21:40:18 GMT Walter Dnes wrote: |
| 2 |
> On Wed, Jan 24, 2018 at 11:43:31AM +0000, Peter Humphrey wrote |
| 3 |
> |
| 4 |
> > On Tuesday, 23 January 2018 18:27:21 GMT Walter Dnes wrote: |
| 5 |
> > |
| 6 |
> > Yes, I do have them both installed already. |
| 7 |
> > |
| 8 |
> > > Is this the official Pale Moon, or an unofficial build? |
| 9 |
> > |
| 10 |
> > It's www-client/palemoon-bin-27.7.1::palemoon. I don't know whether |
| 11 |
> > that's "official", because when I "layman -a palemoon" I'm told it's |
| 12 |
> > not an official overlay. Different officialdoms, I suppose. |
| 13 |
> |
| 14 |
> Disclosure... I'm a volunteer for the Pale Moon project (not an official |
| 15 |
> spokesman). |
| 16 |
|
| 17 |
Yes, I'd gathered that. Kudos to you :) |
| 18 |
|
| 19 |
> I do a contributed build for Pentium3-class machines. My idea of |
| 20 |
> "official" is obviously "from the Pale Moon website". Can you do a quick- |
| 21 |
> n-dirty install from the official tarball to check if the icon problem |
| 22 |
> happens with the official Pale Moon? This test will install into $HOME/pm |
| 23 |
> |
| 24 |
> 1) Go to http://linux.palemoon.org/download/mainline/ and download the |
| 25 |
> appropriate (32 or 64 bit) tarball for your system. |
| 26 |
> |
| 27 |
> 2) killall palemoon # Ignore error message if Pale Moon not running. |
| 28 |
> |
| 29 |
> 3) rm -rf $HOME/pm && mkdir $HOME/pm # Start from a known state |
| 30 |
> |
| 31 |
> 4) tar -C $HOME/pm -xvjf <tarball_name> # Extract tarball |
| 32 |
> |
| 33 |
> 5) $HOME/pm/palemoon/palemoon # Launch Pale Moon |
| 34 |
> |
| 35 |
> Note; this install is self-contained. It does not splatter stuff all |
| 36 |
> over various library directories. Does the icon problem still happen |
| 37 |
> with the official tarball? |
| 38 |
|
| 39 |
'Fraid so, and I still get those undefined-symbol errors I mentioned. |
| 40 |
|
| 41 |
> > This is with gcc 4.9.4, and I get the same with gcc 6.4.0. |
| 42 |
> |
| 43 |
> 6.3.0 builds Pale Moon OK on profile 13. I'll soon be doing the switch |
| 44 |
> over to 17 on my 32-bit desktop. You might be able to get things working |
| 45 |
> with custom flags for the Pale Moon ebuild using package.env as per... |
| 46 |
> https://wiki.gentoo.org/wiki//etc/portage/package.env |
| 47 |
|
| 48 |
Hmm. I'll have to put my thinking-cap on for that. Maybe tomorrow. This is |
| 49 |
what portage wants to do (I'm on profile 17.0): |
| 50 |
|
| 51 |
[ebuild N #] www-client/palemoon-27.7.1::palemoon USE="alsa dbus |
| 52 |
devtools gtk2 official-branding optimize -debug -ffmpeg (-gtk3) -jemalloc - |
| 53 |
necko-wifi -pulseaudio -shared-js -system-bzip2 -system-libevent -system- |
| 54 |
libvpx -system-libwebp -system-sqlite -system-zlib -threads -valgrind - |
| 55 |
webrtc" CPU_FLAGS_X86="sse sse2" 0 KiB |
| 56 |
|
| 57 |
-- |
| 58 |
Regards, |
| 59 |
Peter. |
Archives