That was fine. The only thing that would be a problem is publishing before any official release announcement is made (regardless of OS)stevepusser wrote: ↑2019-09-01, 20:09Was it OK that the packages in my OBS repo were ready on 30 August? I just assumed your static Linux builds were done when I saw the release announcement on the home page.
What happened to 28.7 for Linux?
Moderator: trava90
Forum rules
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
-
- Pale Moon guru
- Posts: 35637
- Joined: 2011-08-28, 17:27
- Location: Motala, SE
Re: What happened to 28.7 for Linux?
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
-
- Board Warrior
- Posts: 1277
- Joined: 2017-06-06, 07:38
Re: What happened to 28.7 for Linux?
The error is due to glibc version, not GLib. Both are different.New Tobin Paradigm wrote: ↑2019-09-01, 13:31Funny cause the Official System Requirements for Pale Moon for Linux call for GLib 2.22 or higher. But how I built the 32bit version took that back down to 2.17.
BTW, glibc 2.15 was released in 2012. They should really upgrade their OS.
Re: What happened to 28.7 for Linux?
That is what I meant.. What, I was like awake for only 10 minutes when I wrote the post. Are the version numbers not in sync between glib and glibc?
The choices are.. glibc 2.12 (matches EL6) or glibc 2.17 (matches EL7). Obviously Travis was still using CentOS 6 to produce the 32bit builds.. Exactly HOW he managed to do cross-compiling I don't know.. That information is just drawing blanks for me except that there is a record in my head of a procedure but it ONLY works when using the system provided GCC.. it would NOT work using devtoolset UNLESS the build env OS is x86.. And THAT doesn't have any official devtoolset for it.. AND the devtoolset for the x64 version does NOT have packages FOR the x86.. Unless I am missing something.
So what I did was I used a Fedora 32bit version with both what I considered the right combo of compiler and glibc version to produce what got released.. That was after six hours of frantic and unproductive research under what I considered was an emergency situation. Deff not how I wanted to spend my Saturday.
As an update: I am looking into a x86 version of the devtoolset as compiled for and by CloudLinux.. If successful I will be able to build on CentOS 6 and the glibc minimum requirement will be lowered to it's former state. I also have to fudge Python 2.7 on there as well. I will continue down this line of research for the time being. If you people are happy with the performance of GCC 4.9 (which others have reported as working better on purely x86 hardware) I will continue using that compiler version. The choices really are that and 7.3.
But that guy using old ass debian-based whatever should REALLY update his operating system no matter what ends up happening.
The choices are.. glibc 2.12 (matches EL6) or glibc 2.17 (matches EL7). Obviously Travis was still using CentOS 6 to produce the 32bit builds.. Exactly HOW he managed to do cross-compiling I don't know.. That information is just drawing blanks for me except that there is a record in my head of a procedure but it ONLY works when using the system provided GCC.. it would NOT work using devtoolset UNLESS the build env OS is x86.. And THAT doesn't have any official devtoolset for it.. AND the devtoolset for the x64 version does NOT have packages FOR the x86.. Unless I am missing something.
So what I did was I used a Fedora 32bit version with both what I considered the right combo of compiler and glibc version to produce what got released.. That was after six hours of frantic and unproductive research under what I considered was an emergency situation. Deff not how I wanted to spend my Saturday.
As an update: I am looking into a x86 version of the devtoolset as compiled for and by CloudLinux.. If successful I will be able to build on CentOS 6 and the glibc minimum requirement will be lowered to it's former state. I also have to fudge Python 2.7 on there as well. I will continue down this line of research for the time being. If you people are happy with the performance of GCC 4.9 (which others have reported as working better on purely x86 hardware) I will continue using that compiler version. The choices really are that and 7.3.
But that guy using old ass debian-based whatever should REALLY update his operating system no matter what ends up happening.
-
- Board Warrior
- Posts: 1277
- Joined: 2017-06-06, 07:38
Re: What happened to 28.7 for Linux?
Currently I use CentOS 7, but for Pale Moon 27, I used to have a CentOS 6 32-bit chroot on my machine. I also had to build GCC 4.9, which was recommended version at that time, from source while inside the chroot. Another package not available in those repositories was yasm which also needed building from source. And that was most of it other that yum installing Pale Moon build dependencies which are a lot of *-devel packages.
My laptop runs latest Arch Linux and Pale Moon builds produced using method above were fully functional on my system despite a huge difference between "run" and "compile" environments.
Obviously, you can do your own research and this information on chroot is available on the Internet but let me know if you want easy "working" instructions which were adapted from many sources online or want to ask something specific.
Travis also once asked me about how I do 32-builds thinking I was doing something magical like cross-compiling using a 64-bit toolchain, but then he was OK once I told him I was using a simple 32-bit chroot system.
My laptop runs latest Arch Linux and Pale Moon builds produced using method above were fully functional on my system despite a huge difference between "run" and "compile" environments.
Obviously, you can do your own research and this information on chroot is available on the Internet but let me know if you want easy "working" instructions which were adapted from many sources online or want to ask something specific.
Travis also once asked me about how I do 32-builds thinking I was doing something magical like cross-compiling using a 64-bit toolchain, but then he was OK once I told him I was using a simple 32-bit chroot system.
-
- Project Contributor
- Posts: 903
- Joined: 2015-08-01, 18:33
Re: What happened to 28.7 for Linux?
I have to be careful not to mix up GLIB and GLIBC too. GLIB are the GNOME base libraries that GTK+ uses, and GLIBC are the C runtime libraries that pretty much everything uses. The versions of each don't have any relationship.
Re: What happened to 28.7 for Linux?
Once I get the revised build environment setup I will be adjusting the System Requirements on the Pale Moon for Linux site (and hopefully changing the site software over to my new project while I am at it). So that both the browser's 32bit and 64bit requirements are explicit.stevepusser wrote: ↑2019-09-03, 20:46I have to be careful not to mix up GLIB and GLIBC too. GLIB are the GNOME base libraries that GTK+ uses, and GLIBC are the C runtime libraries that pretty much everything uses. The versions of each don't have any relationship.
I am currently pushing for 32bit to require older but not ancient systems (continuing to compile with GCC 4.9) while 64bit will continue to target EL 7 level or higher systems.
I will also look into using the GCC 8 for 64bit builds but I will need bare metal testers to ensure stability of builds using it. Failing that GCC 7.x has been doing a pretty good job.
Additionally, 64bit will be getting a GTK 3 build along side it's GTK 2 build. I see no reason to provide one for 32bit since I am pushing for it to be treated as (reasonably) legacy on the Linux.
Keep in mind, kids, that in the absence of Travis (or someone else interim as a Linux Developer) I can only provide so much help and action in the linuxsphere. Mostly giving a few things some attention on a build or infra level. Oh and coordination. I am good with coordination. (And of course giving orders, but you all know that )
Re: What happened to 28.7 for Linux?
Hi kids.. Wanted to update you 32bit guys on the current state of the special build environment required to provide you with binaries for the Pale Moon.
I have constructed a CentOS 6/GCC 4.9 i386 environment that I intend to use going forward. My test build was successful.. This will mean glibc requirement will be back to 2.12 minimum. We are planning a security update soon but I want one or two of you 32bit people to lend me a hand in testing a build from the new build vm.
If you want to help out.. Please be quick about it because that sec release coming up is coming this week. You are the guys who are gonna be using what I push out so it would be nice to know it works properly.
EDIT: Yes, Dnes, even you.
I have constructed a CentOS 6/GCC 4.9 i386 environment that I intend to use going forward. My test build was successful.. This will mean glibc requirement will be back to 2.12 minimum. We are planning a security update soon but I want one or two of you 32bit people to lend me a hand in testing a build from the new build vm.
If you want to help out.. Please be quick about it because that sec release coming up is coming this week. You are the guys who are gonna be using what I push out so it would be nice to know it works properly.
EDIT: Yes, Dnes, even you.
Re: What happened to 28.7 for Linux?
Here: http://repository.binaryoutcast.com/artifacts/builds/palemoon/palemoon-28.7.1pre.linux-i686.tar.bz2
fc6cee389e002d37463a330c58a32a0553aa81139444b37a28930159103e117c
This SHOULD update to the release version later this week. DO treat it as an unstable though. Test speed and stability but as I said before.. Please be quick about it.
fc6cee389e002d37463a330c58a32a0553aa81139444b37a28930159103e117c
This SHOULD update to the release version later this week. DO treat it as an unstable though. Test speed and stability but as I said before.. Please be quick about it.
Re: What happened to 28.7 for Linux?
@New Tobin Paradigm Hi! I'm testing new-test binary 32bit from this morning... So far everything seems good. Nothing different from the official releases.
I am checking it through the console to see any warn, browser is launched very cleanly as usual. I'm also using ps_mem to see memory usage + top for CPU usage. about:memory (GC+CC+Minimize memory usage) releases the memory properly. OK everything on this field.
It's been a few hours online since today's morning where I started testing. I have downloaded a few files, also watched Youtube clips.
The performance seems quiet. Chats / Disquss / Blogs / Feeds OK.
I'm testing on bare-bone Devuan with ALSA sound, GTK2 Customized theme. GTK theme part seems all right. I'm testing Pale Moon theme Photonic. Browser theme is working without any visible glitchs.
As far as I've tested, everything seems fine to me. Probably anything else may be located along the way, so far nothing malfunction at first sight.
Thank you very much for the interest, care, maintenance on 32bit architecture.
I am checking it through the console to see any warn, browser is launched very cleanly as usual. I'm also using ps_mem to see memory usage + top for CPU usage. about:memory (GC+CC+Minimize memory usage) releases the memory properly. OK everything on this field.
It's been a few hours online since today's morning where I started testing. I have downloaded a few files, also watched Youtube clips.
The performance seems quiet. Chats / Disquss / Blogs / Feeds OK.
I'm testing on bare-bone Devuan with ALSA sound, GTK2 Customized theme. GTK theme part seems all right. I'm testing Pale Moon theme Photonic. Browser theme is working without any visible glitchs.
As far as I've tested, everything seems fine to me. Probably anything else may be located along the way, so far nothing malfunction at first sight.
Thank you very much for the interest, care, maintenance on 32bit architecture.
Re: What happened to 28.7 for Linux?
No, thank you Tokia. That is very very helpful.
-
- Project Contributor
- Posts: 903
- Joined: 2015-08-01, 18:33
Re: What happened to 28.7 for Linux?
The Debian Stable (Buster) builds in my repo, as well as Ubuntu 18.10 and above, are being built with gcc-8, and so far there haven't been any complaints at all about it being unstable.
Is there any news about gcc-9 compatibility work, since that's the default gcc in upstream Debian and Ubuntu?
Is there any news about gcc-9 compatibility work, since that's the default gcc in upstream Debian and Ubuntu?
-
- Astronaut
- Posts: 652
- Joined: 2015-07-30, 20:29
- Location: Vaughan, ON, Canada
Re: What happened to 28.7 for Linux?
I'm now on my backup desktop, a 2008 Dell Dimension 530, Core2 Duo, 3 gigs of ram, running up-to-date Gentoo. So far so good. I have 5 separate sessions (separate profiles) open. Some have multiple tabs. Some have ANM (Advanced Night Mode) extension. I've checked web forums, made a post or two and watched some Youtube. I'll report back later today about my laptop, which runs Slacko Puppy 5.4.
There's a right way
There's a wrong way
And then there's my way
There's a wrong way
And then there's my way
Re: What happened to 28.7 for Linux?
Thank you for the gcc8 report. I am not going to change it for 64bit this coming release but may in the future. Good to know it looks good but I would like more testing outside of debianspace.stevepusser wrote: ↑2019-09-09, 18:28The Debian Stable (Buster) builds in my repo, as well as Ubuntu 18.10 and above, are being built with gcc-8, and so far there haven't been any complaints at all about it being unstable.
Is there any news about gcc-9 compatibility work, since that's the default gcc in upstream Debian and Ubuntu?
GCC 9 as an option.. Well there was some prelim work that happened but nothing was committed toward that end. I suspect that will change in the near future. Do want to keep compatibility so the patches would need to take that into account.
Thank you Dnes. Your service has been noted.Walter Dnes wrote: ↑2019-09-09, 19:25I'm now on my backup desktop, a 2008 Dell Dimension 530, Core2 Duo, 3 gigs of ram, running up-to-date Gentoo. So far so good. I have 5 separate sessions (separate profiles) open. Some have multiple tabs. Some have ANM (Advanced Night Mode) extension. I've checked web forums, made a post or two and watched some Youtube. I'll report back later today about my laptop, which runs Slacko Puppy 5.4.
-
- Astronaut
- Posts: 652
- Joined: 2015-07-30, 20:29
- Location: Vaughan, ON, Canada
Re: What happened to 28.7 for Linux?
The 32-bit build works fine on Puppy Slacko 5.4 (refurbished Lenovo laptop), just like the 28.6 series. It does not launch on 5.2.x series Puppy linux. So this build matches Pale Moon 28.6 series for backwards compatability.
On another note, Gentoo linux is now on gcc-8.3.0. My homebrew builds for my 64-bit desktop run just fine, so that's a good sign.
On another note, Gentoo linux is now on gcc-8.3.0. My homebrew builds for my 64-bit desktop run just fine, so that's a good sign.
There's a right way
There's a wrong way
And then there's my way
There's a wrong way
And then there's my way
Re: What happened to 28.7 for Linux?
Understood and thank you Dnes.
I am declaring linux 32bit officially sorted. Thank you all.
I am declaring linux 32bit officially sorted. Thank you all.
Re: What happened to 28.7 for Linux?
I tried to update from 28.0.1 to 28.7 32bit on puplinux Tahr 605.
According to the log, it seems to have done the update successfully.
Tried both apply update now and apply at next PM start,
but I can't get palemoon to start, not even running from /opt/palemoon.
Where do I look ...?
According to the log, it seems to have done the update successfully.
Tried both apply update now and apply at next PM start,
but I can't get palemoon to start, not even running from /opt/palemoon.
Where do I look ...?
-
- Knows the dark side
- Posts: 4981
- Joined: 2015-12-09, 15:45
Re: What happened to 28.7 for Linux?
If you launch it from a terminal window, does it show any errors that you can share here?
"One hosts to look them up, one DNS to find them and in the darkness BIND them."
Linux Mint 21 Xfce x64 on HP i5-5200 laptop, 12 GB RAM.
AutoPageColor|PermissionsPlus|PMPlayer|Pure URL|RecordRewind|TextFX
Linux Mint 21 Xfce x64 on HP i5-5200 laptop, 12 GB RAM.
AutoPageColor|PermissionsPlus|PMPlayer|Pure URL|RecordRewind|TextFX
Re: What happened to 28.7 for Linux?
I tried to update from 28.0.1 to 28.7 32bit on puplinux Tahr 605.
According to the log, it seems to have done the update successfully.
Tried both apply update now and apply at next PM start,
but I can't get palemoon to start, not even running from /opt/palemoon.
I ran it as terminal and that gave the following (edited ...) messages :
XPCOMGlueload error for file /mnt/sdd/palemoonnew/libxul.so: /usr/libstdc++.so.6 ... not found (required by ... libxul.so
...Couldn't load XPCOM.
According to the log, it seems to have done the update successfully.
Tried both apply update now and apply at next PM start,
but I can't get palemoon to start, not even running from /opt/palemoon.
I ran it as terminal and that gave the following (edited ...) messages :
XPCOMGlueload error for file /mnt/sdd/palemoonnew/libxul.so: /usr/libstdc++.so.6 ... not found (required by ... libxul.so
...Couldn't load XPCOM.
Re: What happened to 28.7 for Linux?
Yeah, that won't be a problem Thursday. If you want to grab that 28.7.1pre to tide you over.
If you read this thread you would know this has been one of the main topics discussed. Did you fully read this thread before posting?
Also, why did you wait so long before updating? It's been just over a year. Do you not believe in updates? You do know much has changed since the second release of Pale Moon on UXP including dozens of critical security fixes.
Quite frankly I am not happy with the combination of obviously old hardware, operating system, and lack of keeping up on browser updates.
If you read this thread you would know this has been one of the main topics discussed. Did you fully read this thread before posting?
Also, why did you wait so long before updating? It's been just over a year. Do you not believe in updates? You do know much has changed since the second release of Pale Moon on UXP including dozens of critical security fixes.
Quite frankly I am not happy with the combination of obviously old hardware, operating system, and lack of keeping up on browser updates.