{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihdl4wn3a5ajudut5kgddlcuegraouispubydlqqb2crojfnqarye",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mixeufvriww2"
  },
  "path": "/viewtopic.php?t=33306&p=272011#p272011",
  "publishedAt": "2026-04-07T22:32:53.000Z",
  "site": "http://forum.palemoon.org",
  "tags": [
    "@athenian200"
  ],
  "textContent": "> Maybe **@athenian200** could look into this and provide his own opinion on the matter as long as he's working on the switch to Python3.\n\nSince you asked for my two cents, here it is...\n\nI will admit, it was a _slight_ nuisance to have to remove --enable-jxl from all my .mozconfig files I have scattered across build environments (same with other old options that got removed), but then again I'm also not building in an environment where opening a text editor in the background during a build would cause issues. It's basically muscle memory for me. And I also get the other side of it, that we don't want tons of redundant options left lying around and bloating the size of the .mozconfig. Though really, the more concerning thing in my mind has actually been people assuming libjxl is broken now because the option to enable it was removed... not realizing it's built by default now.\n\nLike, the one thing to make clear is that for most people, the \"invalid option\" message basically _is_ their notification the option was removed. Though it depends on them knowing how the build system works, and also assumes they aren't running on a RAM and hard-drive constrained environment where running a file manager or a text editor would take up too many system resources. It usually isn't that hard to get a build started up again if it stops. I will offer one tip about editing your .mozconfig that might help a little, though. You should run the editor from the console window, _never_ fire up a file manager just to find it. If you just type vim .mozconfig or emacs .mozconfig in the same directory as you started the build from, you'll open the right file every time, no file manager required. Vim is a console text editor and very light on resources (was designed for old terminals), so it might be worth learning if your environment is constrained.\n\nThe only idea I really have that could work for this, is to build on what Basilisk-Dev did for his browser... vendor a default .mozconfig file that gets copied in as the user's .mozconfig if they don't have one already, and then use that instead of relying on the user to have their own local .mozconfig up-to-date.\n\nSo basically, we'd vendor a default .mozconfig with the application, and treat that default .mozconfig the way CLOBBER is treated now. Basically, if that file gets changed, warn the user the browser's default .mozconfig was changed and that they should double-check their local configuration against the official .mozconfig before trying to build, just like we warn them to clobber if CLOBBER is touched. It should be easy enough to do, and wouldn't require too many changes to the build system. But it would mean every time we touch the build options, we'd _have_ to make sure we remember to update that default .mozconfig provided with the browser, or the same issue would still happen.\n\nI genuinely wonder how often this is a problem, though... if it's mostly the resource-constrained build environment that makes this an issue, or if other users have issues around this? I personally think it's fine the way it is, but also would understand if we want to improve on the situation a little. I think it's something to save for a later date if we do want to change it though, since I currently have my hands full making sure the Python 3 build works across multiple environments. I still have to go through those Linux patches we got from a Debian user, investigate a non-fatal Powershell nuisance on Windows, and figure out why NetBSD isn't working (just got an e-mail about that).\n\n* * *",
  "title": "Browser Development • Re: 34.2.0 build failed, --enable-jxl unknown ??",
  "updatedAt": "2026-04-07T22:32:53.000Z"
}