You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to compile 7.2.1 using pkg-config discovery of sqlite3 fails (correctly)
../configure
...
...
checking for SQLITE3... configure: error: Package requirements (sqlite3 >= 3.11) were not met:
Requested 'sqlite3 >= 3.11' but version of SQLite is 3.7.17
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables SQLITE3_CFLAGS
and SQLITE3_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
note the versions being incompatible with what is specified in the configure scripts.
Lastly, make check using the old sqlite3 library did not result in any failed test cases.
So my question is, is 3.11 really a requirement, or should it really have failed in the 3.3.5 case? I.e. some logic in the configure script seems to be missing when using the explicit library paths.
The text was updated successfully, but these errors were encountered:
See #1721 for the rationale for >= 3.11
We could probably have a check when folks provide SQLITE3_CFLAGS and SQLITE3_LIBS, but it looks like a waste of energy as 3.11 is already ancient by today's standards
Won't fix
Thanks for the comment.
For the record for other readers, older sqlite3 are sufficient, the 3.11 is a performance improvement requirement, but not a functional requirement.
the 3.11 is a performance improvement requirement, but not a functional requirement.
The performance is sometimes horrible with < 3.11, you've been warned, and we don't test against it, and current master requires requires at least 3.8 something I believe
This is a build issue from source.
Trying to compile 7.2.1 using pkg-config discovery of
sqlite3
fails (correctly)However, I can easily bypass this by doing this:
SQLITE3_CFLAGS=/appl/sqlite3/3.3.5/include SQLITE3_LIBS="-L/appl/sqlite3/3.3.5/lib -Wl,-rpath,/appl/sqlite3/3.3.5/lib -lsqlite3" ../configure
note the versions being incompatible with what is specified in the configure scripts.
Lastly,
make check
using the old sqlite3 library did not result in any failed test cases.So my question is, is 3.11 really a requirement, or should it really have failed in the 3.3.5 case? I.e. some logic in the configure script seems to be missing when using the explicit library paths.
The text was updated successfully, but these errors were encountered: