On Mon, Nov 18, 2019 at 3:51 PM Sébastien Labbé <sla...@gmail.com> wrote:
>
>
>
>
> The first try at running make gives me this:
>
>
> [sagelib-9.0.beta6] make[4] : on entre dans le répertoire « 
> /home/slabbe/GitBox/sage/src »
> [sagelib-9.0.beta6] cd . && export                                    \
> [sagelib-9.0.beta6]     SAGE_ROOT=/doesnotexist                               
> \
> [sagelib-9.0.beta6]     SAGE_SRC=/doesnotexist                                
> \
> [sagelib-9.0.beta6]     SAGE_SRC_ROOT=/doesnotexist                           
> \
> [sagelib-9.0.beta6]     SAGE_DOC_SRC=/doesnotexist                            
> \
> [sagelib-9.0.beta6]     SAGE_BUILD_DIR=/doesnotexist                          
> \
> [sagelib-9.0.beta6]     SAGE_PKGS=/home/slabbe/GitBox/sage/build/pkgs         
>        \
> [sagelib-9.0.beta6] && sage-python -u setup.py --no-user-cfg build install
> [sagelib-9.0.beta6] /home/slabbe/GitBox/sage/src/bin/sage-env: ligne 130 : 
> cd: /doesnotexist: Aucun fichier ou dossier de ce type
> [sagelib-9.0.beta6] Warning: overwriting SAGE_ROOT environment variable:
> [sagelib-9.0.beta6] Old SAGE_ROOT=/doesnotexist
> [sagelib-9.0.beta6] New SAGE_ROOT=
> [sagelib-9.0.beta6] Traceback (most recent call last):
> [sagelib-9.0.beta6]   File "setup.py", line 22, in <module>
> [sagelib-9.0.beta6]     import fpickle_setup
> [sagelib-9.0.beta6]   File "/home/slabbe/GitBox/sage/src/fpickle_setup.py", 
> line 8, in <module>
> [sagelib-9.0.beta6]     from six.moves import copyreg
> [sagelib-9.0.beta6] ModuleNotFoundError: No module named 'six'
> [sagelib-9.0.beta6] Makefile:33 : la recette pour la cible « sage » a échouée
> [sagelib-9.0.beta6] make[4]: *** [sage] Erreur 1
> [sagelib-9.0.beta6] make[4] : on quitte le répertoire « 
> /home/slabbe/GitBox/sage/src »
> [sagelib-9.0.beta6]
> [sagelib-9.0.beta6] real    0m0.049s
> [sagelib-9.0.beta6] user    0m0.032s
> [sagelib-9.0.beta6] sys    0m0.012s
> Makefile:1987 : la recette pour la cible « sagelib » a échouée
> make[3]: *** [sagelib] Erreur 2
> make[3] : on quitte le répertoire « /home/slabbe/GitBox/sage/build/make »
> Makefile:1848 : la recette pour la cible « all-start » a échouée
> make[2]: *** [all-start] Erreur 2
> make[2] : on quitte le répertoire « /home/slabbe/GitBox/sage/build/make »
>
> real    0m0.208s
> user    0m0.148s
> sys    0m0.016s
> ***************************************************************
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-start'):
>
> The build directory may contain configuration files and other potentially
> helpful information. WARNING: if you now run 'make' again, the build
> directory will, by default, be deleted. Set the environment variable
> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

IMO this does appear to be a bug though.  If you have an existing
Python 2 build of Sage it should *not* break just because the default
has changed to Python 3.  It appears something is trying to run the
fpickle_setup.py script (whatever that is) with python3 even if it's a
python2 build of Sage.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAOTD34Zr2Een8%2Bvoj%2Bim%3DpP6o_Xm4P6BFZarZ1uDzXa8rc58Wg%40mail.gmail.com.

Reply via email to