Re: [SUSPECTED SPAM] Re: [gentoo-user] Questions about Pale Moon

[Peter Humphrey]

On Friday, 26 January 2018 13:20:04 GMT Walter Dnes wrote:
> On Wed, Jan 24, 2018 at 11:43:31AM +, Peter Humphrey wrote
> 
> > 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?
> 
>   This may or may not be relavant.  I build Pale Moon manually for my
> home machines, using the Mozilla Firefox process.  64-bit builds worked
> fine with GCC-6.4.0 on profile 13.0.  Anything built with GCC-6.x under
> profile 17.0 segfaults in 10-15 seconds after launching Pale Moon.  A
> custom-built GCC-5.4.0 builds a stable Pale Moon.

I haven't yet managed to compile 27.7.1 at all with either GCC 6.4.0 or 
4.9.4, using the palemoon overlay via layman, on profile default/linux/
amd64/17.0/desktop/plasma. I get the loader errors I quoted on Wednesday.

I wonder whether I should try the 17.1 profile...

>   I'm currently doing a test build with GCC-6.4.0 on my 32-bit desktop,
> having just finished the migration to 17.0.  Current ICEWM 1.4.2 (and
> 1.4.0) crashes out of X to a text console when I click on the menu bar
> at the bottom.  I've dropped back to 1.3.12-r1 ...and copied the ebuild
> over to a local overlay.  I'm not liking profile 17.0 far.

-- 
Regards,
Peter.

[SUSPECTED SPAM] Re: [gentoo-user] Questions about Pale Moon

[Walter Dnes]

On Wed, Jan 24, 2018 at 11:43:31AM +, Peter Humphrey wrote
> 
> 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?

  This may or may not be relavant.  I build Pale Moon manually for my
home machines, using the Mozilla Firefox process.  64-bit builds worked
fine with GCC-6.4.0 on profile 13.0.  Anything built with GCC-6.x under
profile 17.0 segfaults in 10-15 seconds after launching Pale Moon.  A
custom-built GCC-5.4.0 builds a stable Pale Moon.

  I'm currently doing a test build with GCC-6.4.0 on my 32-bit desktop,
having just finished the migration to 17.0.  Current ICEWM 1.4.2 (and
1.4.0) crashes out of X to a text console when I click on the menu bar
at the bottom.  I've dropped back to 1.3.12-r1 ...and copied the ebuild
over to a local overlay.  I'm not liking profile 17.0 far.

-- 
Walter Dnes 
I don't run "desktop environments"; I run useful applications

Re: [SUSPECTED SPAM] Re: [gentoo-user] Questions about Pale Moon

[Peter Humphrey]

On Wednesday, 24 January 2018 21:40:18 GMT Walter Dnes wrote:
> On Wed, Jan 24, 2018 at 11:43:31AM +, 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).

Yes, I'd gathered that. Kudos to you :)

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

'Fraid so, and I still get those undefined-symbol errors I mentioned.

> > This is with gcc 4.9.4, and I get the same with gcc 6.4.0.
> 
> 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

Hmm. I'll have to put my thinking-cap on for that. Maybe tomorrow. This is 
what portage wants to do (I'm on profile 17.0):

[ebuild  N#] www-client/palemoon-27.7.1::palemoon  USE="alsa dbus 
devtools gtk2 official-branding optimize -debug -ffmpeg (-gtk3) -jemalloc -
necko-wifi -pulseaudio -shared-js -system-bzip2 -system-libevent -system-
libvpx -system-libwebp -system-sqlite -system-zlib -threads -valgrind -
webrtc" CPU_FLAGS_X86="sse sse2" 0 KiB

-- 
Regards,
Peter.

[SUSPECTED SPAM] Re: [gentoo-user] Questions about Pale Moon

[Walter Dnes]

On Wed, Jan 24, 2018 at 11:43:31AM +, 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   # 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 
I don't run "desktop environments"; I run useful applications