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
Since we meanwhile require a system python to let Sage build anyway, we don't have to wait with building ATLAS until Sage's python has been built, as ATLAS doesn't install any Python libraries, but only its spkg-install has been rewritten in Python quite a while ago.
This requires two things:
Remove the dependency of ATLAS on $(PYTHON) (which means Sage's python2 or python3 package) in its dependencies.
Make ATLAS' spkg-install again a shell script, renaming the current one to spkg-install.py, say, where the shell script just contains
#!/bin/shexec python spkg-install.py
This is necessary because sage-spkg checks whether Sage'spython is already installed if an spkg-install script starts with #! ... python, and bails out otherwise:
atlas-3.10.2.p2
====================================================
Setting up build directory for atlas-3.10.2.p2
Finished set up
Error: The spkg-install script is written in Python, but the Python
package is not yet installed in Sage. You should add $(PYTHON)
as dependency in build/pkgs/atlas/dependencies
make[2]: *** [.../sage/local/var/lib/sage/installed/atlas-3.10.2.p2] Error 1
(Note that this message originates from a build where the Makefile was broken, such that the make dependency of ATLAS on the python package was fulfilled by $(PYTHON) accidentally being empty. So one won't get this message unless the Makefile is corrupted.)
Rather orthogonal to that, our top-level configure doesn't contain any check for python yet, although currently at least sage-download-file and sage-uncompress-spkg require (a system) python (in the beginning of the build). I'll address that on another ticket -- see #21116.
Since we meanwhile require a system python to let Sage build anyway, we don't have to wait with building ATLAS until Sage's python has been built, as ATLAS doesn't install any Python libraries, but only its
spkg-install
has been rewritten in Python quite a while ago.This requires two things:
Remove the dependency of ATLAS on
$(PYTHON)
(which means Sage'spython2
orpython3
package) in itsdependencies
.Make ATLAS'
spkg-install
again a shell script, renaming the current one tospkg-install.py
, say, where the shell script just containsThis is necessary because
sage-spkg
checks whether Sage'spython
is already installed if anspkg-install
script starts with#! ... python
, and bails out otherwise:(Note that this message originates from a build where the
Makefile
was broken, such that themake
dependency of ATLAS on the python package was fulfilled by$(PYTHON)
accidentally being empty. So one won't get this message unless theMakefile
is corrupted.)Rather orthogonal to that, our top-level
configure
doesn't contain any check forpython
yet, although currently at leastsage-download-file
andsage-uncompress-spkg
require (a system) python (in the beginning of the build). I'll address that on another ticket -- see #21116.Depends on #30350
CC: @vbraun
Component: packages: standard
Keywords: sage-spkg dependencies spkg-install
Reviewer: Michael Orlitzky
Issue created by migration from https://trac.sagemath.org/ticket/21114
The text was updated successfully, but these errors were encountered: