Skip to content

Conversation

@pmenzel
Copy link
Collaborator

@pmenzel Paul Menzel (pmenzel) commented Oct 8, 2026 •

Tested on tldr (dfnmilter, inmilter) and done (pbackup).

SHA3-256 checksum matches the one listed on
https://sqlite.org/download.html:

    454e45f61c6bd75b7420e7190732dea03ce6639c63ada47bbc592f67fc340338

Since 3.48.0, the autoconf tarball ships an autosetup configure script,
so bee does not detect the build type anymore, and the options change:

- `--enable-dynamic-extensions` is gone:

      Error: Unknown option --dynamic-extensions

  Use its successor `--enable-load-extension`. Keep `--enable-threadsafe`
  and `--enable-readline` explicit, although they are the defaults: an
  explicit `--enable-readline` makes configure fail, if readline is not
  found, instead of silently building the shell without line editing.
- Without `--soname`, the library gets *no* SONAME at all. Pass
  `--soname=legacy` to keep `libsqlite3.so.0`, which all consumers
  link against.
- The new build adds `RPATH /usr/lib`, which 3.38.5 did not have:

      0x000000000000000f (RPATH)              Library rpath: [/usr/lib]

  Pass `--disable-rpath` to drop it.
- Use `--fts3`, `--fts4`, `--fts5`, `--rtree`, `--geopoly`, and
  `--dbstat` instead of the defines, so that `PRAGMA compile_options`
  of the library lists everything 3.38.5 did. The new build only adds
  upstream defaults:

      > DIRECT_OVERFLOW_READ
      > ENABLE_PERCENTILE
      < MAX_FUNCTION_ARG=127
      > MAX_FUNCTION_ARG=1000
      < MAX_PAGE_COUNT=1073741823
      > MAX_PAGE_COUNT=0xfffffffe

The library file is now `libsqlite3.so.3.53.4`, with `libsqlite3.so.0`
and `libsqlite3.so` pointing to it.

Tested with beesh on hotelcalifornia: FTS3/FTS5, R*Tree, JSON and dbstat
work, and the Python 3 `sqlite3` module built against 3.38.5 loads the
new library.

Assisted-by: claude-opus-5.5 (Claude Code)
@pmenzel Paul Menzel (pmenzel) merged commit 3371c54 into master Oct 9, 2026
@donald
Copy link
Collaborator

Bad timing (https://sqlite.org/releaselog/3_54_0.html) ? OTOH we don't like .0 versions :-)

Sign in to join this conversation on GitHub.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants