The plot thickens : I tried to upgrade to 9.3.beta3. ./configure orked (ith 
the usual claimfor system packages already installed…), but make fails : 

make[2] : on entre dans le répertoire « /usr/local/sage-9/build/make »
make[2]: warning: -j8 forced in submake: resetting jobserver mode.
make --no-print-directory /usr/local/sage-9/local/var/lib/sage/installed/.dummy
make[3]: « /usr/local/sage-9/local/var/lib/sage/installed/.dummy » est à jour.
make --no-print-directory /usr/local/sage-9/local/var/lib/sage/installed/.dummy
make[3]: « /usr/local/sage-9/local/var/lib/sage/installed/.dummy » est à jour.
make --no-print-directory /usr/local/sage-9/local/var/lib/sage/installed/.dummy
make[3]: « /usr/local/sage-9/local/var/lib/sage/installed/.dummy » est à jour.
make --no-print-directory /usr/local/sage-9/local/var/lib/sage/installed/.dummy
make[3]: « /usr/local/sage-9/local/var/lib/sage/installed/.dummy » est à jour.
make --no-print-directory doc all-sage
make --no-print-directory sage_conf-no-deps
make --no-print-directory nodeenv-no-deps
make --no-print-directory jupyterlab-no-deps
cd '/usr/local/sage-9/build/pkgs/sage_conf' && . 
'/usr/local/sage-9/src/bin/sage-env-config' && . 
'/usr/local/sage-9/src/bin/sage-env' && . 
'/usr/local/sage-9/build/bin/sage-build-env-config' && sage-logger -p 
'/usr/local/sage-9/build/pkgs/sage_conf/spkg-install' 
'/usr/local/sage-9/logs/pkgs/sage_conf-none.log'
sage-logger -p 'sage --pip install -r 
"/usr/local/sage-9/build/pkgs/nodeenv/requirements.txt"' 
'/usr/local/sage-9/logs/pkgs/nodeenv.log'
sage-logger -p 'sage --pip install -r 
"/usr/local/sage-9/build/pkgs/jupyterlab/requirements.txt"' 
'/usr/local/sage-9/logs/pkgs/jupyterlab.log'
[sage_conf-none] Installing 
[sage_conf-none] Traceback (most recent call last):
[sage_conf-none]   File "/usr/local/sage-9/build/pkgs/sage_conf/src/setup.py", 
line 1, in <module>
[sage_conf-none]     from setuptools import setup
[sage_conf-none] ModuleNotFoundError: No module named 'setuptools'
[sage_conf-none] Error: could not determine package name
[sage_conf-none] 
********************************************************************************
[sage_conf-none] Error uninstalling a previous version of
[sage_conf-none] 
********************************************************************************
make[4]: *** [Makefile:2165 : sage_conf-no-deps] Erreur 1
[jupyterlab] /usr/local/sage-9/local/bin/python3: No module named pip
make[3]: *** [Makefile:2165 : 
/usr/local/sage-9/local/var/lib/sage/installed/sage_conf-none] Erreur 2
[nodeenv] /usr/local/sage-9/local/bin/python3: No module named pip
make[3]: *** Attente des tâches non terminées....
make[4]: *** [Makefile:2107 : nodeenv-no-deps] Erreur 1
make[4]: *** [Makefile:2107 : jupyterlab-no-deps] Erreur 1
make[3]: *** [Makefile:2107 : nodeenv] Erreur 2
make[3]: *** [Makefile:2107 : jupyterlab] Erreur 2
make[2]: *** [Makefile:1768 : all-start] Erreur 2
make[2] : on quitte le répertoire « /usr/local/sage-9/build/make »

real    0m0,277s
user    0m0,545s
sys    0m0,086s
***************************************************************
Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all-start'):

* package:         sage_conf-none
  last build time: 7 déc. 10:10
  log file:        /usr/local/sage-9/logs/pkgs/sage_conf-none.log

It is safe to delete any log files and build directories, but they
contain information that is helpful for debugging build problems.
WARNING: If you now run 'make' again, the build directory of the
same version of the package will, by default, be deleted. Set the
environment variable SAGE_KEEP_BUILT_SPKGS=yes to prevent this.

Suggestions ?
make[1]: *** [Makefile:33 : all-start] Erreur 1
make[1] : on quitte le répertoire « /usr/local/sage-9 »
make: *** [Makefile:13 : all] Erreur 2

real    0m0,814s
user    0m1,144s
sys    0m0,206s

This also happens after re-running ./bootstrap…

Suggestions ?
Le lundi 7 décembre 2020 à 09:52:38 UTC+1, Emmanuel Charpentier a écrit :

> Setup :
>
> - Debian testing, amd64, 16 GB RAM
>
> - Sage 9.3.beta2 compiled from `develop` git branch, configured to use as 
> much system packages as possible.
>
> A recent system update upgraded system’s python to3.9.rc1. Result :
>
> charpent@zen-book-flip:~$ sage Traceback (most recent call last): File 
> "/usr/local/sage-9/src/bin/sage-ipython", line 9, in <module> from 
> sage.misc.banner import banner ModuleNotFoundError: No module named 'sage'
>
> Suggestions ?
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/7735ca29-1efe-4498-adc6-ba5f5736b90fn%40googlegroups.com.

Reply via email to