Dear SageMath,

SageMath 9.8 beta 4 failed to build on this system:

$ uname -a
Linux 4.4.0-17763-Microsoft #2268-Microsoft Thu Oct 07 16:36:00 PST 2021 
x86_64 x86_64 x86_64 GNU/Linux
$ which python3
/usr/bin/python3
$ python3 --version
Python 3.10.8
$ ~/sage-9.8/b4/b4.0/local/var/lib/sage/venv-python3.10.8/bin/python3 
--version
Python 3.10.8
$ wheel version
wheel 0.34.2
$ ~/sage-9.8/b4/b4.0/sage -pip list | grep 'wheel'
wheel                         0.37.1
$ ls -l ~/sage-9.8/b4/b4.0/logs/pkgs | wc -l
192

Questions:

   1. Is ~/sage-9.8/b4/b4.0/local/var/lib/sage/venv-python3.10.8/bin/python3 
   freshly built or a "copy and paste" of  /usr/bin/python3? 
   Can /usr/bin/python3 be used 'as is where is' for SageMath?
   
   2. Why different versions of "wheel"? ( 'wheel ' on this system was 
   installed after SageMath 9.8 beta 4 was released and the version was 
   decided by the system). Is version 0.37.1 better for SageMath 9.8 than 
   0.34.2
   
   3. Subsequent to a failed build (because of 'Error building a wheel for 
   jupyter_jsmol-2022.1.0'), the build process always invokes make for 
   'sagelib-9.8.beta4' and 'sagemath_doc_html-none'. This takes about an hour 
   on this system. Is this necessary? Can it be avoided?
   
   4. What does the option "--config-settings" do in the context of the 
   following excerpt from the log file:
   
   "Package 'jupyter_jsmol' is currently not installed
   No legacy uninstaller found for 'jupyter_jsmol'; nothing to do
   Installing jupyter_jsmol-2022.1.0
   
   Usage:
     
   /home/hph/sage-9.8/b4/b4.0/local/var/lib/sage/venv-python3.10.8/bin/python3 
   -m pip wheel [options] <requirement specifier> ...
     
   /home/hph/sage-9.8/b4/b4.0/local/var/lib/sage/venv-python3.10.8/bin/python3 
   -m pip wheel [options] -r <requirements file> ...
     
   /home/hph/sage-9.8/b4/b4.0/local/var/lib/sage/venv-python3.10.8/bin/python3 
   -m pip wheel [options] [-e] <vcs project url> ...
     
   /home/hph/sage-9.8/b4/b4.0/local/var/lib/sage/venv-python3.10.8/bin/python3 
   -m pip wheel [options] [-e] <local project path> ...
     
   /home/hph/sage-9.8/b4/b4.0/local/var/lib/sage/venv-python3.10.8/bin/python3 
   -m pip wheel [options] <archive url/path> ...
                                                                           
                                          
     
   /home/hph/sage-9.8/b4/b4.0/local/var/lib/sage/venv-python3.10.8/bin/python3 
   -m pip wheel [options] <archive url/path> ...
   
   no such option: --config-settings
   
   
***********************************************************************************************************************************************
   Error building a wheel for jupyter_jsmol-2022.1.0
   
   
***********************************************************************************************************************************************
   
   5. Last but not least, how to debug and fix this issue with "Error 
   installing package jupyter_jsmol-2022.1.0" on this system after going to 
   the debug subshell?  
   
   From the log file:
   "If you want to try to fix the problem yourself, *don't* just cd to
   
/home/hph/sage-9.8/b4/b4.0/local/var/lib/sage/venv-python3.10.8/var/tmp/sage/build/jupyter_jsmol-2022.1.0
 
   and type 'make' or whatever is appropriate.
   Instead, the following commands setup all environment variables
   correctly and load a subshell for you to debug the error:
     (cd 
   
'/home/hph/sage-9.8/b4/b4.0/local/var/lib/sage/venv-python3.10.8/var/tmp/sage/build/jupyter_jsmol-2022.1.0'
 
   && '/home/hph/sage-9.8/b4/b4.0/sage' --buildsh)
   When you are done debugging, you can type "exit" to leave the subshell."
   
   
Your help is greatly appreciated.

With best wishes and regards,

phi

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a4587dfd-fa28-480f-a064-3dda0d37f51dn%40googlegroups.com.

Reply via email to