{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihwjz6avenjmat4jcrqdf6y6acuhr4v6vsyh3aq3b76cuevt5g2nu",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mlbr62tdugx2"
  },
  "path": "/viewtopic.php?t=33412&p=273637#p273637",
  "publishedAt": "2026-05-07T16:36:47.000Z",
  "site": "http://forum.palemoon.org",
  "tags": [
    "@Drugwash",
    "@TOPSRCDIR"
  ],
  "textContent": "> I'd like to build Basilisk-Qt6 in a Debian VM and take it for a spin. But first I'd like @Drugwash's errors below to be addressed, and to find out if we have a .mozconfig we can use:\n\nThis is the mozconfig I was using during testing. I use Clang for development and release builds, so you'll need to remove the clang stuff if you want to use GCC and make adjustments if you'd like to try Pale Moon or Epyrus with QT6 instead. I have a separate mozconfig I was using for debugging, basically just set optimizations to -O1 and set --enable-debug and --enable-debug-symbols and --disable-strip. Tried to comment it for you the best I can.\n\nCODE:\n\n\n    # objdirmk_add_options MOZ_OBJDIR=@TOPSRCDIR@/obj-qt6# Set Basilisk version to date timestampexport BASILISK_VERSION=1# Use clang/llvm toolchainexport CC=\"clang\"export CXX=\"clang++\"export AR=\"llvm-ar\"export NM=\"llvm-nm\"export RANLIB=\"llvm-ranlib\"export LD=ld.lld# Force LLVM for HOST tools as wellexport HOST_CC=clangexport HOST_CXX=clang++export HOST_AR=llvm-arexport HOST_RANLIB=llvm-ranlibexport HOST_NM=llvm-nmexport HOST_LD=ld.lld# Ensure static archives always get a symbol table (__.SYMDEF).# UXP build logic assumes ar creates this implicitly,# but with ThinLTO + LLVM bitcode that is no longer guaranteed.# Without the 's' flag, ld/lld will fail with:# \"archive has no index; run ranlib to add one\"# This is especially critical for HOST tools (mbsdiff, mar, etc.).export ARFLAGS=crsexport HOST_ARFLAGS=crsexport ARFLAGS=crsexport HOST_ARFLAGS=crs# ThinLTO with Clang/LLVM. -Wl,--undefined-version is needed due to differences between GNU ld and lldexport LDFLAGS=\"-flto=thin -fuse-ld=lld -Wl,--undefined-version\"#No ThinLTO#export LDFLAGS=\"-fuse-ld=lld -Wl,--undefined-version\"# O3 is stable and produces faster binaries than O2, -w to suppress all warnings, -flto=thin for ThinLTOac_add_options --enable-optimize=\"-O3 -w -flto=thin\"#No ThinLTO#ac_add_options --enable-optimize=\"-O3 -w\"# Standard build options for Basiliskac_add_options --enable-application=basiliskac_add_options --enable-default-toolkit=cairo-qt6ac_add_options --enable-jemallocac_add_options --enable-stripac_add_options --enable-devtoolsac_add_options --enable-av1ac_add_options --enable-webrtcac_add_options --enable-gamepadac_add_options --enable-pieac_add_options --enable-update-channel=releaseac_add_options --disable-testsac_add_options --disable-debugac_add_options --disable-necko-wifiac_add_options --enable-updaterac_add_options --with-pthreadsac_add_options --enable-official-brandingexport MOZILLA_OFFICIAL=1ac_add_options --x-libraries=/usr/lib64export MOZ_PKG_SPECIAL=qt6\n\nI haven't worked on it in a few days, still has a lot of bugs to fix. I'd be using this version daily if we got it merged in and would be willing to maintain upgrading to future QT versions as they come out since upgrading QT releases is substantially easier than upgrading GTK releases.\n\n\n> Or, if all we're doing anyway is trying to provide an integration layer, then why not run on Wine (since win32 isn't going away in the foreseeable future) and do away with native Linux builds? All things that roll around in my head reading this discussion.\n\nThis would break support for everyone not using x86. I know nobody else is using LoongArch like I am, but I know for sure some people use aarch64 Linux builds on hardware like Raspberry Pi.\n\n* * *",
  "title": "Browser Development • Re: Linux Pale Moon with Qt toolkit",
  "updatedAt": "2026-05-07T16:36:47.000Z"
}