When building and installing from the v3.50.2 autoconf tarball, the installed sqlite3.pc file is not providing the full set of necessary flags on RHEL-derived platforms (specifically Rocky Linux, as reported by a user at https://github.com/sparklemotion/sqlite3-ruby/issues/634).

Before the 3.48.0 autosetup change, the installed sqlite3.pc file would emit the following on Rocky Linux:

$ pkg-config --libs --static path/to/sqlite3.pc
-L/path/to/sqlite3/3.47.2/lib -lsqlite3 -lz -lm -ldl -lpthread

However, as of 3.48.0, it emits:

$ pkg-config --libs --static path/to/sqlite3.pc
-L/path/to/sqlite3/3.50.2/lib -lsqlite3 -lm -lz

Using these flags results in linker failures, for example: undefined reference to symbol 'dlclose@@GLIBC_2.2.5'.

I'm the maintainer of the downstream sqlite3 Ruby library, and I'm finding it tricky to figure out how to correctly link against the built sqlite3 across a wide variety of platforms. Specifically, the missing -ldl is problematic since libdl.so does not exist on some platforms (e.g., Musl Linux) and so the installer can't simply blindly add it to the link line.

For now, I'll figure out a workaround downstream; but I'm wondering if the SQLite maintainers are planning to restore any of the previous autoconf behaviors in the "autoconf" distribution of SQLite?

Thanks much,

-mike