Ubuntu 14.04, 16.04, 16.10, 17.04, Debian 7, 8, 9 Pale Moon repositories

Support and discussions for the x86/x64 Linux version of Pale Moon.

Moderators: trava90, satrow

Walter Dnes
Astronaut
Astronaut
Posts: 506
Joined: Thu, 30 Jul 2015, 20:29
Location: Vaughan, ON, Canada

Re: Ubuntu 14.04, 16.04, 16.10, 17.04, Debian 7, 8, 9 Pale Moon repositories

Postby Walter Dnes » Thu, 25 Jan 2018, 01:36

stevepusser wrote:Could it be as simple as passing -std=c99 or -std-c++11 to the CXXFLAGS in mozconfig or exporting that in build environment?

1) I found that I had to add ac_add_options --enable-stdcxx-compat to mozconfig to enable the SSE build to run on distros based on older libs (yes; with backported security fixes).

2) Near the top of the webpage https://gcc.gnu.org/gcc-6/changes.html
The default mode for C++ is now -std=gnu++14 instead of -std=gnu++98.


3) I don't know if the next item is Gentoo-specific, or widespread. As of profile 17.0 and GCC-6.4.0, PIC/PIE is forced down Gentoo users' throats. Linking between PIC and non-PIC code causes problems, so Gentoo users have to emerge -e world, i.e. rebuild every last package on the system, to ensure that everything is built PIC/PIE. Are other distros going with PIC/PIE, and would this cause problems for Pale Moon?
There's a right way
There's a wrong way
And then there's my way

User avatar
stevepusser
Lunatic
Lunatic
Posts: 340
Joined: Sat, 01 Aug 2015, 18:33
Location: California

Re: Ubuntu 14.04, 16.04, 16.10, 17.04, Debian 7, 8, 9 Pale Moon repositories

Postby stevepusser » Thu, 25 Jan 2018, 03:04

I'm pretty sure that Debian Stretch's build system enforces PIC/PIE hardening by default, and Pale Moon builds OK with gcc-4.9 there. I tried some options to try from the Giggle to get it to build correctly on Ubuntu's 17.10's libc6 2.26 and gcc-4.9, but still get the isinfinite error. I'll try to add your mozconfig and see what happens.

I just discovered how to add Debian Buster (testing) builds to the OBS, and launched gcc-4.9 builds for it, but no doubt will get the same libc6 2.2.6 error there for Pale Moon. I also tried looking in the bootleg Pale Moon builds on the OBS to see any patches for the problem were there already, but nothing.

User avatar
stevepusser
Lunatic
Lunatic
Posts: 340
Joined: Sat, 01 Aug 2015, 18:33
Location: California

Re: Ubuntu 14.04, 16.04, 16.10, 17.04, Debian 7, 8, 9 Pale Moon repositories

Postby stevepusser » Thu, 25 Jan 2018, 20:11

Code: Select all

ac_add_options --enable-stdcxx-compat   


makes the builds fail right away with gcc-4.9. I'll try a gcc-6 build with that and put them up for manual download and testing,
since you say your gcc-6 builds with that seem to be stable, and gcc-6 does not have trouble with isinfinite and libc6 2.26.

Walter Dnes
Astronaut
Astronaut
Posts: 506
Joined: Thu, 30 Jul 2015, 20:29
Location: Vaughan, ON, Canada

Re: Ubuntu 14.04, 16.04, 16.10, 17.04, Debian 7, 8, 9 Pale Moon repositories

Postby Walter Dnes » Fri, 26 Jan 2018, 03:19

stevepusser wrote:since you say your gcc-6 builds with that seem to be stable, and gcc-6 does not have trouble with isinfinite and libc6 2.26.

Actually, the current Gentoo glibc ebuild is 2.25-r9, so no info about 2.26. I've done some experimenting...

  • GCC-6.4.0 native 32+64 bit builds (not the CentOS chroot) under the now-deprecated Gentoo profile 13.0 (without PIC/PIE) worked fine
  • GCC-6.4.0 native 64-bit builds under the "new and improved" profile 17.0 :thumbdown: (with PIC/PIE) segfault 10-15 seconds after startup
  • native 64-bit builds. using custom-built GCC-5.4.0 under profile 17.0 work fine. This post is coming from my "build machine" using a 5.4.0-built Pale Moon. My regular (32-bit) desktop is currently rebuilding all 541 packages migrating to profile 17.0
My current working hypothesis is that we have 2 problems
1) glibc 2.26
2) building Pale Moon with PIC/PIE

To test out my hypothesis, I'll have to custom build GCC-6.3 and 6.4 using the script I PM'd you. The native Gentoo GCC-6.4.0 builds a segfaulting Pale Moon. If a custom-built GCC-6.4.0 produces stable Pale Moon, I may be on to something.
There's a right way
There's a wrong way
And then there's my way

Walter Dnes
Astronaut
Astronaut
Posts: 506
Joined: Thu, 30 Jul 2015, 20:29
Location: Vaughan, ON, Canada

Re: Ubuntu 14.04, 16.04, 16.10, 17.04, Debian 7, 8, 9 Pale Moon repositories

Postby Walter Dnes » Fri, 26 Jan 2018, 04:35

Walter Dnes wrote:To test out my hypothesis, I'll have to custom build GCC-6.3 and 6.4 using the script I PM'd you. The native Gentoo GCC-6.4.0 builds a segfaulting Pale Moon. If a custom-built GCC-6.4.0 produces stable Pale Moon, I may be on to something.

So much for that idea. 64-bit native build in Gentoo (profile 17.0) with custom-built GCC-6.3.0 segfaults. GCC-5.4.0 build works. GCC-5.5.0 (minor bugfix) has been released. I assume that will work too.
There's a right way
There's a wrong way
And then there's my way

User avatar
stevepusser
Lunatic
Lunatic
Posts: 340
Joined: Sat, 01 Aug 2015, 18:33
Location: California

Re: Ubuntu 14.04, 16.04, 16.10, 17.04, Debian 7, 8, 9 Pale Moon repositories

Postby stevepusser » Fri, 26 Jan 2018, 19:08

Ubuntu 17.10 has gcc-5.5 in their standard repo. I'll try a test build against that in the OBS. Debian testing (Buster)no longer has gcc-5, but it's still being updated in the the unstable Sid repo, so I could try adding that to a Buster repo.

The Arch AUR is building against gcc-5 and glibc 2.26. The changelog mentions a fix for 2.26, but I really can't see what it is from this commit: https://aur.archlinux.org/cgit/aur.git/ ... b4b64b1abf
Last edited by stevepusser on Fri, 26 Jan 2018, 19:22, edited 1 time in total.

User avatar
stevepusser
Lunatic
Lunatic
Posts: 340
Joined: Sat, 01 Aug 2015, 18:33
Location: California

Re: Ubuntu 14.04, 16.04, 16.10, 17.04, Debian 7, 8, 9 Pale Moon repositories

Postby stevepusser » Fri, 26 Jan 2018, 19:41

Nope, gcc-5.5 with glibc 2.26 throws the same isinfinite error on 17.10. Like I said, I can't see what the AUR changed in their build to putatively fix that.

The PM devs say that glibc 2.26 is busted. Not their fault.

I could try to add glibc 2.25 into the repo with a trick version like "2.26upgrade.really2.25" so the system would think it's newer...
Last edited by stevepusser on Fri, 26 Jan 2018, 19:49, edited 1 time in total.

User avatar
New Tobin Paradigm
Banned user
Banned user
Posts: 4417
Joined: Tue, 09 Oct 2012, 19:37

Re: Ubuntu 14.04, 16.04, 16.10, 17.04, Debian 7, 8, 9 Pale Moon repositories

Postby New Tobin Paradigm » Fri, 26 Jan 2018, 19:51

We can likely work around it with some ifdefing IF we can get the glib version number into a define.. But we would like some help to do that.. This way it will work in multiple configurations.
I hate Pod Six. Tch, I don't even know why we have a Pod Six. Total suck Pod.
[ ニュー・トビン・パラダイム ]

Goven35
New to the forum
New to the forum
Posts: 1
Joined: Fri, 26 Jan 2018, 21:08

Re: Ubuntu 14.04, 16.04, 16.10, 17.04, Debian 7, 8, 9 Pale Moon repositories

Postby Goven35 » Fri, 26 Jan 2018, 21:19

symbolic links are broken because /usr/lib/palemoon-nonsse2/palemoon doesn't exist.

Code: Select all

sudo rm /usr/bin/palemoon
sudo ln -s '/usr/lib/palemoon/palemoon' /usr/bin/palemoon
sudo apt-get install palemoon-nonsse2


Pour supprimer les liens cassés:

Code: Select all

sudo rm /usr/share/icons/hicolor/16x16/apps/palemoon.png
sudo rm /usr/share/icons/hicolor/32x32/apps/palemoon.png
sudo rm /usr/share/icons/hicolor/48x48/apps/palemoon.png
sudo rm /usr/share/icons/hicolor/128x128/apps/palemoon.png
sudo rm /usr/share/pixmaps/palemoon.png


Pour créer les nouveaux:

Code: Select all

sudo ln -s /usr/lib/palemoon/browser/chrome/icons/default/default16.png /usr/share/icons/hicolor/16x16/apps/palemoon.png
sudo ln -s /usr/lib/palemoon/browser/chrome/icons/default/default32.png /usr/share/icons/hicolor/32x32/apps/palemoon.png
sudo ln -s /usr/lib/palemoon/browser/chrome/icons/default/default48.png /usr/share/icons/hicolor/48x48/apps/palemoon.png
sudo ln -s /usr/lib/palemoon/browser/icons/mozicon128.png /usr/share/icons/hicolor/128x128/apps/palemoon.png
sudo ln -s /usr/lib/palemoon/browser/icons/mozicon128.png /usr/share/pixmaps/palemoon.png

.

calibrations
Moongazer
Moongazer
Posts: 12
Joined: Tue, 26 Dec 2017, 15:35

Re: Ubuntu 14.04, 16.04, 16.10, 17.04, Debian 7, 8, 9 Pale Moon repositories

Postby calibrations » Fri, 26 Jan 2018, 23:15

Looking at the date on that commit I would guess it's related to the following comment on the AUR (ctrl-f AndyRTR for the source)
# fix build with glibc 2.26
sed -i "s:xlocale:locale:" Pale-Moon/intl/icu/source/i18n/digitlst.cpp

Probably not the fix you want!

Off-topic:
On the subject of clang, I've tried a clang 5.0.1 build mostly out of curiosity and have not experienced any crashes... yet. Obviously cannot recommend it for distribution just on that.

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 21182
Joined: Sun, 28 Aug 2011, 17:27
Location: 58.5°N 15.5°E
Contact:

Re: Ubuntu 14.04, 16.04, 16.10, 17.04, Debian 7, 8, 9 Pale Moon repositories

Postby Moonchild » Fri, 26 Jan 2018, 23:22

stevepusser wrote:Nope, gcc-5.5 with glibc 2.26 throws the same isinfinite error on 17.10. Like I said, I can't see what the AUR changed in their build to putatively fix that.

The PM devs say that glibc 2.26 is busted. Not their fault.

I could try to add glibc 2.25 into the repo with a trick version like "2.26upgrade.really2.25" so the system would think it's newer...


it's a known issue.
glibc 2.26 is broken, and you need to rebuild gcc with glibc 2.26 built from the TIP of the branch (not the release commit) to fix the math macro issue.
I still find it pretty bad that the glibc maintainers haven't released a 2.26-1 or whatnot version to address this, and require you to build your compiler from source... but I guess "welcome to the wonderful world of GNU" is all this boils down to.
Improving Mozilla code: You know you're on the right track with code changes when you spend the majority of your time deleting code.

"The wisest men follow their own direction." - Euripedes

Walter Dnes
Astronaut
Astronaut
Posts: 506
Joined: Thu, 30 Jul 2015, 20:29
Location: Vaughan, ON, Canada

Re: Ubuntu 14.04, 16.04, 16.10, 17.04, Debian 7, 8, 9 Pale Moon repositories

Postby Walter Dnes » Sat, 27 Jan 2018, 02:04

My 32-bit Gentoo machine, profile 17.0, GCC-6.4.0 built a seemingly stable native Pale Moon. It's been running for sevral hours with no crashes so far. On the down side, I had to drop back to a previous version of ICEWM (Window Manager) to keep X running properly (for all apps).

That's with the glibc-2.25-r9 ebuild. Gentoo Bugzilla indicates multiple apps, besides Pale Moon, having problems with glibc-2.26 https://bugs.gentoo.org/buglist.cgi?quicksearch=GLIBC%202.26&list_id=3824634
There's a right way
There's a wrong way
And then there's my way

User avatar
stevepusser
Lunatic
Lunatic
Posts: 340
Joined: Sat, 01 Aug 2015, 18:33
Location: California

Re: Ubuntu 14.04, 16.04, 16.10, 17.04, Debian 7, 8, 9 Pale Moon repositories

Postby stevepusser » Sat, 27 Jan 2018, 03:49

Goven35 wrote:symbolic links are broken because /usr/lib/palemoon-nonsse2/palemoon doesn't exist.

Code: Select all

sudo rm /usr/bin/palemoon
sudo ln -s '/usr/lib/palemoon/palemoon' /usr/bin/palemoon
sudo apt-get install palemoon-nonsse2


Pour supprimer les liens cassés:

Code: Select all

sudo rm /usr/share/icons/hicolor/16x16/apps/palemoon.png
sudo rm /usr/share/icons/hicolor/32x32/apps/palemoon.png
sudo rm /usr/share/icons/hicolor/48x48/apps/palemoon.png
sudo rm /usr/share/icons/hicolor/128x128/apps/palemoon.png
sudo rm /usr/share/pixmaps/palemoon.png


Pour créer les nouveaux:

Code: Select all

sudo ln -s /usr/lib/palemoon/browser/chrome/icons/default/default16.png /usr/share/icons/hicolor/16x16/apps/palemoon.png
sudo ln -s /usr/lib/palemoon/browser/chrome/icons/default/default32.png /usr/share/icons/hicolor/32x32/apps/palemoon.png
sudo ln -s /usr/lib/palemoon/browser/chrome/icons/default/default48.png /usr/share/icons/hicolor/48x48/apps/palemoon.png
sudo ln -s /usr/lib/palemoon/browser/icons/mozicon128.png /usr/share/icons/hicolor/128x128/apps/palemoon.png
sudo ln -s /usr/lib/palemoon/browser/icons/mozicon128.png /usr/share/pixmaps/palemoon.png

.


Thanks for the bug report...I'll fix that tomorrow. I did find out how to request more RAM and disk space on the OBS for the build machines by uploading a _constraints xml file along with the source files which lists what you want, but then you have to wait in queue for the more powerful machines to become available. I tested backporting llvm-5.0 and mesa 17.3.3 to Stretch--it worked, plus they built very quickly.

User avatar
stevepusser
Lunatic
Lunatic
Posts: 340
Joined: Sat, 01 Aug 2015, 18:33
Location: California

Re: Ubuntu 14.04, 16.04, 16.10, 17.04, Debian 7, 8, 9 Pale Moon repositories

Postby stevepusser » Sat, 27 Jan 2018, 19:22

A new version of palemoon-nonsse2 is building that'll hopefully fix the broken links problem.

It looks like Ubuntu 17.10 users won't get successful Pale Moon builds in the repository, then. Since Debian testing Buster is "rolling", hopefully eventually a fixed version of glibc will make its way into it. I have a successful build of gcc-4.9 for Buster. I tried building a newer version of glibc 2.26 from Debian Experimental in Buster, but it failed. We probably don't want that in a repo, anyway...I just wanted to see if that would fix the build.

Walter Dnes
Astronaut
Astronaut
Posts: 506
Joined: Thu, 30 Jul 2015, 20:29
Location: Vaughan, ON, Canada

Re: Ubuntu 14.04, 16.04, 16.10, 17.04, Debian 7, 8, 9 Pale Moon repositories

Postby Walter Dnes » Sun, 28 Jan 2018, 00:52

stevepusser wrote:It looks like Ubuntu 17.10 users won't get successful Pale Moon builds in the repository, then.

Gentoo has some ebuilds as "-bin" wrappers, especially for huge builds that take hours or run out of ram on an older memory-constrained machine, e.g. libreoffice-bin and firefox-bin. I.e. download the compiled linux tarball from upstream, and extract it, rather than building from source.

Does Ubuntu .deb/whatever have the ability to download a compile tarball from linux.palemoon.org, and extract it to /usr/local and then "ln -sf /usr/local/palemoon/palemoon /usr/bin/palemoon". For "defensive programming", consider renaming an existing "/usr/local/palemoon" to "/usr/local/palemoon.old", and only deleting it if the install succeeds.
There's a right way
There's a wrong way
And then there's my way

smoki
Hobby Astronomer
Hobby Astronomer
Posts: 20
Joined: Fri, 19 Jan 2018, 05:34

Re: Ubuntu 14.04, 16.04, 16.10, 17.04, Debian 7, 8, 9 Pale Moon repositories

Postby smoki » Sun, 28 Jan 2018, 03:11

stevepusser wrote: I tried building a newer version of glibc 2.26 from Debian Experimental in Buster, but it failed.


That one in experimental is glibc 2.27 actually it is marked as 2.26.9000 but is real 2.27 base branch ;) Upstream relase of 2.27 needs to happen in next couple days, then will be pushed in sid probably in a month or so.

Basically once Ubuntu LTS stops importing from Debian, which is about March 1st... expect all these new things to be pushed.

BTW, did you tried building palemoon but for 18.04 and on Launchpad? If that woks i guess palemoon itself does not need fixes, that would just mean how Ubunut does not care much about interim releases

edit: actually do not try it, as i see they didn't imported yet artful and bionic are quite the same, while unstable is a lot ahead of bionic currently :D

http://changelogs.ubuntu.com/changelogs ... /changelog
http://metadata.ftp-master.debian.org/c ... _changelog
Last edited by smoki on Sun, 28 Jan 2018, 04:11, edited 8 times in total.

User avatar
stevepusser
Lunatic
Lunatic
Posts: 340
Joined: Sat, 01 Aug 2015, 18:33
Location: California

Re: Ubuntu 14.04, 16.04, 16.10, 17.04, Debian 7, 8, 9 Pale Moon repositories

Postby stevepusser » Mon, 29 Jan 2018, 03:31

smoki wrote:
stevepusser wrote: I tried building a newer version of glibc 2.26 from Debian Experimental in Buster, but it failed.


That one in experimental is glibc 2.27 actually it is marked as 2.26.9000 but is real 2.27 base branch ;) Upstream relase of 2.27 needs to happen in next couple days, then will be pushed in sid probably in a month or so.

Basically once Ubuntu LTS stops importing from Debian, which is about March 1st... expect all these new things to be pushed.

BTW, did you tried building palemoon but for 18.04 and on Launchpad? If that woks i guess palemoon itself does not need fixes, that would just mean how Ubunut does not care much about interim releases

edit: actually do not try it, as i see they didn't imported yet artful and bionic are quite the same, while unstable is a lot ahead of bionic currently :D

http://changelogs.ubuntu.com/changelogs ... /changelog
http://metadata.ftp-master.debian.org/c ... _changelog


I really am not an Ubuntu user, so don't know how to create or use a PPA on Launchpad.

About putting the already-compiled binary files into a .deb package: yes, that's fairly easy to do. Debian does some of that with the proprietary Nvidia driver in the non-free section, and we do it for Firefox over on MX Linux, especially since it's now impossible to compile from source on any released version of Debian. That was how I was packaging palemoon-atom, in fact. I'll look into that tomorrow for 17.10.

User avatar
stevepusser
Lunatic
Lunatic
Posts: 340
Joined: Sat, 01 Aug 2015, 18:33
Location: California

Re: Ubuntu 14.04, 16.04, 16.10, 17.04, Debian 7, 8, 9 Pale Moon repositories

Postby stevepusser » Mon, 29 Jan 2018, 18:05

Re: repacks of the binaries into debs, isn't that already being done by László Kovács? I wouldn't want to reinvent the wheel.

smoki
Hobby Astronomer
Hobby Astronomer
Posts: 20
Joined: Fri, 19 Jan 2018, 05:34

Re: Ubuntu 14.04, 16.04, 16.10, 17.04, Debian 7, 8, 9 Pale Moon repositories

Postby smoki » Wed, 31 Jan 2018, 03:49

stevepusser wrote: I really am not an Ubuntu user, so don't know how to create or use a PPA on Launchpad.


I use Debian not Ubuntu at all really. But AFAIU Launchpad overall is similar as OBS, just Ubuntu-only... i spotted how LPD allows building for 18.04 (but OBS don't yet) so thought that if you are in hurry maybe to give it a try, as maybe there is no that glibc bug which appear on 17.10 an so on.

About putting the already-compiled binary files into a .deb package: yes, that's fairly easy to do. Debian does some of that with the proprietary Nvidia driver in the non-free section, and we do it for Firefox over on MX Linux, especially since it's now impossible to compile from source on any released version of Debian. That was how I was packaging palemoon-atom, in fact. I'll look into that tomorrow for 17.10.


Yeah, compiling for others to use could be hard. Rebuiding on every distro and every point is even harder, as code needs to be smart and to allows all that... which is the hardest and i guess code became messy that way :D

Well, if it does not build somewhere just repack official one... that is easiest.
Last edited by smoki on Wed, 31 Jan 2018, 03:59, edited 6 times in total.

User avatar
stevepusser
Lunatic
Lunatic
Posts: 340
Joined: Sat, 01 Aug 2015, 18:33
Location: California

Re: Ubuntu 14.04, 16.04, 16.10, 17.04, Debian 7, 8, 9 Pale Moon repositories

Postby stevepusser » Thu, 01 Feb 2018, 22:40

Well, 27.2.2 is being built from source for the working repos. I'll look into bundling the binaries into debs for Buster and 17.10, I promise.


Return to “Pale Moon for Linux”

Who is online

Users browsing this forum: No registered users and 6 guests