{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibjkspzqsl7zu7gxqrthgzjwqlzrwlawvphuvyi7xfa7ac7chgdca",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mj3elhcud732"
  },
  "path": "/viewtopic.php?t=33306&p=272097#p272097",
  "publishedAt": "2026-04-09T17:10:10.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "For the record, this --enable-jxl bit me too when compiling 34.2.0. As MC said, it was caught early in the process, and I just removed that line from my .mozconfig and was back in business--no big deal.\n\nWhile I understand that it might be frustrating to encounter a new build failure due to an obsolete option, silently ignoring it would not be helpful in the long run. Personally, I figure MC has enough on his plate without having to design and build an external GUI application to hand-hold people through the build process. Just my two cents...\n\n* * *",
  "title": "Browser Development • Re: 34.2.0 build failed, --enable-jxl unknown ??",
  "updatedAt": "2026-04-09T17:10:10.000Z"
}