Skip to content
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

Build instructions and documentation don’t work with current WSL Ubuntu #38820

Open
2 tasks done
G4DCP opened this issue Oct 17, 2024 · 2 comments
Open
2 tasks done

Comments

@G4DCP
Copy link

G4DCP commented Oct 17, 2024

Steps To Reproduce

  1. Install SageMath in a Conda environment on WSL (Ubuntu 22.04).
  2. Run sage and follow the instructions provided by the initial help message, which suggest running tutorial() to access the tutorial.
    3.When running tutorial(), Sage throws an error, stating that the documentation doesn’t exist and that it needs to be built.
  3. Attempting to build the documentation using sage -docbuild tutorial html or sage -docbuild all html results in errors about missing directories and an undefined SAGE_ROOT.

Expected Behavior

I expect the tutorial and documentation to be accessible as indicated by Sage's help message. Running sage -docbuild tutorial html should successfully build the documentation.

Actual Behavior

The tutorial doesn’t run, and Sage throws errors about missing documentation files.
Building the documentation manually with sage -docbuild results in errors like FileNotFoundError or SAGE_ROOT undefined.
Even after manually downloading the documentation files and setting appropriate environment variables, the process still fails.

Additional Information

No response

Environment

Operating System: WSL (Windows Subsystem for Linux)
Ubuntu 22.04 (and similar issues on Debian)
SageMath Version: 10.4 (Conda version from conda-forge)
Python Version: 3.11 (managed via Conda)

Checklist

  • I have searched the existing issues for a bug report that matches the one I want to file, without success.
  • I have read the documentation and troubleshoot guide
@G4DCP G4DCP added the t: bug label Oct 17, 2024
@G4DCP
Copy link
Author

G4DCP commented Oct 17, 2024

A general comment I have tried wsl and native debian 12 neither gives a straight forward path to getting a running sage.

I'm sorry for my poor typing but I am 72 years old and disabled(Parkingsons).

I have a test lab as I am an ex computer consultant

The windows is windows11 Version 23H2 (OS build 22631.2317)

--
Peter Hull G4DCP

@kh-abd-kh
Copy link

can you be more explicit, i have run through a similar problem for sage-10.4.beta9.
Yes, the install didn't generate the help documents at all. and moreover when you call sage
it doesn't launch sage.
you have to call sage manually by ./sage-10.4.beta9/sage
But, then I generated them with docbuild.
In this case, i used from my sage dir
find -name "doctree" -type d
then it gave me
./local/share/doc/sage/doctrees
and you have to call them manually from your browser
google-chrome
then
file:///home/mabd/sage-10.4.beta9/local/share/doc/sage/html/en/index.html
change mabd to your user name.
But this for sage-10.4.beta9, i am not sure if it is the same
but just i hope to help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants