New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade sqlite3 to 3.27.1 #27303
Comments
comment:3
Builds without a hitch.
which is identical in all details to the one already reported before this patch. ==> New commits:
|
Commit: |
Author: Emmanuel Charpentier |
comment:4
Replying to @EmmanuelCharpentier: Note that this doesn not fix my original issue, which is attributable to another (yet unknown) problem... |
comment:5
Still good to update this. To the buildbots it goes. |
Reviewer: Travis Scrimshaw |
comment:6
Replying to @EmmanuelCharpentier:
I guess you may have solved the first failure out of many. What's next? |
Changed branch from u/charpent/upgrade_sqlite3_to_3_27_1 to |
comment:8
Replying to @kiwifb:
Nothing "reasonable" that I've tried worked : it seems that using the library entails the use of configuration executables which have the library path hardcoded, or possibly vice-versa. So I went unreasonable an installed the library from source via sage -sh under $SAGE_LOCAL. This worked. And is a pain in the *ss... Thanks for your help ! |
Changed commit from |
Rationale : see this sage-devel post and its followup.
Tarball : https://sqlite.org/2019/sqlite-autoconf-3270100.tar.gz
CC: @kiwifb
Component: packages: standard
Author: Emmanuel Charpentier
Branch:
09ae5f1
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/27303
The text was updated successfully, but these errors were encountered: