{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicx4bkktvkps2qgpt4jolf46djah7qjax6fquwzkon6kg5e7kmeeu",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3ml2tmpolbma2"
  },
  "path": "/viewtopic.php?t=27873&p=273440#p273440",
  "publishedAt": "2026-05-04T21:42:31.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> Instead of waiting, I went and ran the build myself, buuut, the version still reads 34.2.0 like from the last time, though it recompiled a bunch of files and took half the time it normally does. Build system bug? Better to delete objdir and get it to recompile everything?\n>\n> Or what do self-builders do?\n>\n> FWIW, NSS library version reads like written in the changelog.\n\nMy recommended strategy is something like this, assuming you're like me and don't pick a custom name for your objdir:\n\n1.\n\nCODE:\n\n\n    cd Pale-Moon\n\n(go to the directory you cloned Pale Moon into).\n2.\n\nCODE:\n\n\n    rm -rf obj*\n\n(I don't trust ./mach clobber, it's burned me before)\n3.\n\nCODE:\n\n\n    rm platform/old-configure && rm platform/js/src/old-configure\n\n(Make 100% sure old-configure is regenerated from the .in file, shouldn't be needed but again, I've been burned before)\n4.\n\nCODE:\n\n\n    git pull\n\n(Make sure you have the latest changes)\n5.\n\nCODE:\n\n\n    git checkout 34.2.2_Release\n\n(Ensures the version pointer is setup correctly, otherwise you'll either get an outdated one or one indicating an alpha)\n6.\n\nCODE:\n\n\n    git submodule update\n\n(Ensures the platform is at the right commit for that release of Pale Moon, without you having to dig around in platform manually)\n7.\n\nCODE:\n\n\n    ./mach build\n\n8.\n\nCODE:\n\n\n    ./mach run\n\n* * *",
  "title": "Contributed 3rd Party Builds • Re: Pale Moon x86-64 SSE2/AVX2",
  "updatedAt": "2026-05-04T21:42:31.000Z"
}