First Build Success!

[Bilbo47]

Buh ZING guh! Finished my first-ever build+package Then tested out the browser. Hurdles:
- new laptop with Win11 (previous one, ten years old, quit doing wifi)
- download and install the tools and source
- Avoid build failures from running out of disk space:
- delete cache folders all over the windows partition (60 GB with now 1G free) Source+build-output takes 8.7GB
- move chrome-flavor browser profile to data partition (32 GB with now 12G free) Tools take 6.1GB
- put in the time to follow instructions
Old dog, new tricks

[vannilla]

GG as they say!

[MasterSlenderTR]

I also made my first Pale Moon build today and it took 11 minutes to build.

[UCyborg]

I managed to compile it about a year ago on Raspberry Pi 5. May attempt to build the latest version in the near future.

There was some oddity in behavior of my bank's website on this build specifically, the script hung on login page and couldn't login. The site worked fine on amd64 build.

[Drugwash]

Yup, first Pale Moon build for me too, last night. Alleviates a couple burdens, considering my OS (Linux Mint 19.2) is old and unsupported.
Had to add a PPA and install gcc-9 and g++-9 backports from there since officially the system only had the 7 and 8 versions available officially, and those are not supported anymore by the PM code. All other tools were already installed since I did build other apps previously.
The git system pissed me off as it could not retrieve only its own data (the .git folders) and insisted on downloading the entire trunk despite the files being already there, downloaded as archives. Waste of time on extremely low (128kB/s) bandwidth.
The .mozconfig file should've been a breeze considering the official sample (which should be updated!) but it was not. After a few trials and errors finally discovered I had to use the compilers' short names (as seen above) not the detailed names as in the sample:

Code: Select all

export CC=gcc-9
export CXX=g++-9

After that the build started and after about three hours I had a working browser. Why three hours? Because it's an old (2009) notebook with an old CPU (i5 M460) and only 8GB of RAM - maximum allowed - which was also running a few other applications.

All this because the Nuck-TH versions I had used after the official release lost compatibility with Ubuntu 18.04 - on which Mint 19.2 is based - have one of the libraries (libmozsqlite3.so) requiring a GLib version (2.28) higher than my system allows (2.27), and until now I had streamlined that library from another build kindly provided some time ago by a nice user, but in PM 3.38.0 the SQLite3 version has been bumped (as per the release notes) and the older library could have potentially created problems. I read somewhere that one could download the headers for older GLib versions from some GitHub repo and include the desired header in order to allow backward compatibility but didn't want to bother Nuck-TH with such requests.

Well, now I can do it myself regardless of the long compilation time without relying on third parties. That is, until some truly breaking change creeps in. And then... I don't know.

[jobbautista9]

I also made my first Pale Moon build today and it took 11 minutes to build.

Damn, that's crazy fast for a build from what's essentially a clobber (i.e. from scratch / no preexisting build progress)! And looking at your computer's specs in your signature explains why lol. I bet if we got the whole codebase de-unified it still would've been less than 20 minutes in your setup!