CIRCLE WITH A DOT

@fcbsd i just woke up from my nap, having had a wonderful dream. and your screenshot is better than said dream. thank you.

My port is ready for submission; I will soon submit my port to the OpenBSD Ports Team for review.

This branch shows what I will send:

Cookie monster!

(codeberg.org)

Branch name labelled submit1, because I anticipate that they may ask for a few changes. So the expected 2nd draft would be sent to submit2, and then submit3, and so on.

Yes. With any luck, they *might* merge my patch for 7.9 - my changes, relative to www/mozilla-firefox, are quite conservative and done in the most surgical way possible.

Just doing some minor polishing, ready for submission to openbsd ports team.

They're already in release mode, so who knows if this will land before OpenBSD 7.9. I hope I can get it in the release.

LibreWolf is similar enough to FireFox, and my port is conservatively-enough engineered relative to www/mozilla-firefox that it fits well into their infrastructure, with little friction. For all intents and purposes, it is essentially the same browser as FireFox, just without the enshittification.

I have important news: my LibreWolf port for OpenBSD now *works perfectly*!

See: https://codeberg.org/vimuser/librewolf-openbsd-port

Latest patch: https://codeberg.org/vimuser/librewolf-openbsd-port/commit/b66909dff671dfae9350b3db84c60b0a32cff9e9

I compiled the master branch on OpenBSD -current (7.9 snapshot).

I rewrote the port again, this time making only the most surgical changes relative to www/mozilla-firefox.

LibreWolf uses mozconfig, so OpenBSD CONFIGURE_ARGS has no effect; I provide a patched mozconfig at build time.

*Everything works*. I rocked out to some tunes, and read some news.

there is a lot of overlap. openbsd's firefox port already adds a bunch of hardened autoconf (./configure) options, that librewolf also does. librewolf and openbsd are two peas in a pod.

it baffles me that nobody tried porting librewolf before i did. i mean, someone did, but i'm unsure if they sent it to openbsd. they simply maintained a package repo themselves, but stopped after obsd 7.1

i couldn't find their sources anymore, so i started from scratch, with my own fresh librewolf port.

because librewofl uses a mozconfig, the cli-based configure options in www/mozilla-firefox are useless for librewolf.

but i can't just patch mozconfig, because variables like e.g. $PREFIX are used by openbsd ports.

what i have to do then: put a custom mozconfig is files/

have e.g. @PREFIX@ in there, and sed search/replace with the variable

do this in pre-configure, in the Makefile. that's my next job.

yes. i *will* tame this ungodly build system.

Adding configure options from /home/leah/portdev/ports-pobj/librewolf-149.0.2/librewolf-149.0.2-2/mozconfig
--enable-application=browser
--allow-addon-sideload
--disable-crashreporter
--disable-debug
--disable-default-browser-agent
--disable-tests
--disable-updater
--disable-cargo-incremental
--enable-hardening
--enable-stl-hardening
--enable-optimize
--enable-release
--enable-rust-simd
--with-app-name=librewolf

^ no --enable-replace-malloc or --enable-jemalloc

yay

absolutely bird-brained build system. gnu autotools, plus mozilla = pain

i feel like the french guy in the matrix, when he just keeps saying "ass of shit, motherfucker, piece of shit" and so on, repeatedly, in french (that's what he's saying to neo when he says he loves the french language because of how cursing with it is like, and i quote, "rubbing your ass in silk")

Nom de Dieu de putain de bordel de merde de saloperie de connard d'enculé de ta mère, firefox.

yes.

FUN FACT: i hate mozilla.

but the actual place to patch is mozconfig (file) in the root of the extracted tarball directory

i... couldn't find this in git grep earlier, because of .gitignore. so i found it manually. librewolf's build system was still adding the malloc-replace options. it should work now.

this is literally the only problem with the librewolf port. needing to disable mozjemalloc. then it should work.

+ac_add_options --enable-application=browser
+
+ac_add_options --allow-addon-sideload
+ac_add_options --disable-crashreporter
+ac_add_options --disable-debug
+ac_add_options --disable-default-browser-agent
+ac_add_options --disable-tests
+ac_add_options --disable-updater
+ac_add_options --disable-cargo-incremental
+ac_add_options --enable-hardening
+ac_add_options --enable-stl-hardening
+ac_add_options --enable-optimize
+ac_add_options --enable-release
+ac_add_options --enable-rust-simd

ALSO FUN FACT:

in that same file, lw/mozconfig.new, librewolf is enabling a bunch of hardening options that openbsd *also enables* on www/mozilla-firefox, but they seem to be entirely redundant on the openbsd port. i can remove most of the extra autoconf options in www/librewolf since librewolf is already applying them!

yes

librewolf 143's lw/mozconfig.new doesn't have --enable-replace-malloc and --enable-jemalloc in it. but that same file *does* have these, in librewolf 149.

in other words: I said it was bollocks, but it probably wasn't. there *is* an incompatibility with mozilla's custom allocator, on openbsd, but www/mozilla-firefox isn't using it. www/librewolf is! because librewolf is awesome, and cares about its linux users, so wants to give them a 0.5% performance increase. yes.

yes.

yes

i may have found it

+# allow replacing malloc manually, will not affect regular systems
+# not compatible with ac_add_options --disable-jemalloc, which only works when preloading custom malloc
+ac_add_options --enable-replace-malloc
+ac_add_options --enable-jemalloc

librewolf 149 enables these options, but 143 didn't. this is from lw/mozconfig.new, which doesn't exist in firefox.

so earlier, i may have been correct, not wrong. gonna patch lw/mozconfig.new to remove this, and re-test building.

I downloaded the src tarball of firefox 149.0.2 and did git init / git add -A . / git commit -m test, inside it.

then i extracted librewolf 149.0.2 tarball and moved the .git from my firefox directory into it, and did: git add -A . , then git commit -m change

now i have all the changes librewolf made, in bulk. i'm analysing those changes. i will find the smoking gun somewhere in this massive diff.

there is librewolf source.git, with its own build system and patching. but i'll check tarballs.

No! It wasn't bollocks! Or maybe it was. Idk

I re-did my port locally, only modifying www/mozilla-firefox in the least invasive way possible, without replacing/rewriting www/mozilla submodule.

Still the same malloc-related build errors on LibreWolf - BUT FIREFOX BUILDS AND WORKS FINE.

So now I'm analysing the code differences between LibreWolf 149.0.2 and FireFox 149.0.2 in unhinged detail. I now believe it may be a modification LibreWolf has done since v143, that breaks the build on OpenBSD.

and i know this because i built www/mozilla-firefox myself. and ran it. and lamented for a while.

my port is broken. firefox's allocator is fine.

update regarding my librewolf openbsd port: everything i said earlier about mozilla's allocator is a load of bollocks. firefox is the same code (where the allocator is concerned. librewolf doesn't touch it) and builds perfectly without patching, and runs perfectly.

rather than fix my cursed port, i'm just doing it from scratch, properly this time - no removing www/mozilla. i'll just make it piggyback off of www/mozilla, like other moz projects in obsd.

eg. www/tor-browser also uses www/mozilla

@fun and this is my debian desktop:

that text is actually a png file. i made the errors from earlier today (failed librewolf build) a wallpaper. the weird eye photo is captured from a specific frame in the movie Mad Max, just before the nightrider's car blows up with him in it.