-
-
Notifications
You must be signed in to change notification settings - Fork 528
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
Refine python3's SAGE_SPKG_DEPCHECK: Remove sqlite #30559
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:9
I don't really understand m4 syntax, but for sqlite, it looks like |
comment:10
The "depcheck" macro is used generally for avoiding a problem with conflicting shared libraries. Here, if we install Now, as the ticket summary explains, ACTUALLY we never use our libsqlite3 for anything other than building python3. So because of that, I think that we could, as you say, remove the depcheck for sqlite3 from spkg-configure.m4 However, if we ever add another package (providing a shared library linked into a Python module) that ALSO uses libsqlite3, then we would have to put the depcheck back... |
comment:11
Moreover, again because python3 is the unique package that uses sqlite3 directly, if system python3 is available, we do not have to build sqlite3 from SPKG even if we don't find system sqlite3. |
comment:12
This is all rather complicated, and I am not sure if our current spkg-configure framework is able to express it cleanly. But I think it would be very valuable to sort it out -- the missing sqlite (headers) are probably the top reason why we might reject python3 at least on macOS |
comment:13
We would have to pay attention if another package were added to use |
Author: Matthias Koeppe |
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Reviewer: John Palmieri |
comment:23
Thanks! |
comment:24
Note: there is no libsqlite3.so and I don't have sqlite3-devel installed
|
comment:27
this seems to need testing on Cygwin |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:29
Cygwin test now running at https://github.com/mkoeppe/sage/actions/runs/358167921 |
Changed reviewer from John Palmieri to John Palmieri, https://github.com/mkoeppe/sage/actions/runs/358167921 |
comment:30
The Cygwin tests look okay to me. Shall we merge it? |
comment:31
I haven't yet seen a Cygwin test to proceed to actually running Sage because of the general fragility of the multi-stage GH actions (I restarted the workflow several times...). But I think we can proceed anyway, it should not hold up this improvement. |
comment:32
Okay, let's try again, then. |
Changed reviewer from John Palmieri, https://github.com/mkoeppe/sage/actions/runs/358167921 to John Palmieri |
comment:33
Thanks! |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Changed branch from u/mkoeppe/refine_python3_s_sage_spkg_depcheck to |
Changed commit from |
Currently we have
SAGE_SPKG_DEPCHECK([sqlite libpng bzip2 xz libffi], ...)
, which causes system python3 to be rejected on many systems.We should review whether this can be made more fine-grained.
SAGE_SPKG_DEPCHECK
is specifically for checking whether we are going to install a shared library that may interfere with a system-provided version of the same shared library that the package is linked against.Package
sqlite
....elliptic_curves
only seems to use the Python module sqlite - it does not depend on sqlite itself.cryptominisat
does not seem to depend on sqlite at all.In this ticket, we remove these unnecessary dependencies and the sqlite depcheck for python3; and set
sqlite
as "not required" if system python3 will be used.Follow-up tickets may address the following dependencies:
SAGE_SPKG_DEPCHECK
: libpng, bzip2, xz, libffixz
represents both the shared libraryliblzma
and thexz
binary.See also:
CC: @orlitzky @dimpase @slel @mwageringel @kiwifb @antonio-rojas @embray
Component: build: configure
Author: Matthias Koeppe
Branch:
4731840
Reviewer: John Palmieri
Issue created by migration from https://trac.sagemath.org/ticket/30559
The text was updated successfully, but these errors were encountered: