search

3-manifolds / sagedocker

The kitchen sink with SnapPy, SageMath, Regina, and friends
6 stars 2 forks source link

Cannot rebuild sage #2

Open mkoeppe opened 2 years ago

mkoeppe commented 2 years ago

The Sage installation in computop/sage:9.5 has several issues that prevent rebuilding when changes are made to Sage.

I ran into this while setting up computop/sage as a VS Code devcontainer for Sage development, https://trac.sagemath.org/ticket/33671

The issues and workarounds for them are described in: https://git.sagemath.org/sage.git/diff/.devcontainer/devcontainer-computop-sage.json?id=8ec5393e16da7b211d4ee060b1dc34dc0facae52

NathanDunfield commented 2 years ago

Thanks for reporting this Matthias, but could you expand on what is wrong? I looked at the json file you linked to, but I didn't know that the computop/sage image supported rebuilding Sage at all and pari seems to work just fine for me. Our script for building Sage just goes with the defaults, so I'm not sure why rebuilding pari and nauty would fix anything.

mkoeppe commented 2 years ago

I think after installing Sage, some of the following scripts in https://github.com/3-manifolds/sagedocker/tree/master/sage/scripts clobber parts of the Sage installation.

NathanDunfield commented 2 years ago

Hmm, we do add some additional software to the $SAGE_LOCAL tree, mostly various topology Python packages, and also mess with the Jupyter(-Lab) config. So that I can debug, what's a specific command that results in an error?

mkoeppe commented 2 years ago

I didn't know that the computop/sage image supported rebuilding Sage at all

True, what is in /sage is not sufficient to do any rebuilds. /sage/src has the complete sources but the top-level Makefile and configure script are missing and sage -b just fails with an unhelpful error.

The devcontainer script uses its own source tree mounted in the container and configures it to re-use the /sage/local installation prefix.

culler commented 2 years ago

I am not sure if this is relevant, but there is now a symlink sage/local/venv to a venv which contains a lot of the stuff that used to go in sage/local. I am guessing that whatever we put into sage/local now needs to move to the venv.

On Tue, May 31, 2022 at 8:33 AM Nathan Dunfield @.***> wrote:

Hmm, we do add some additional software to the $SAGE_LOCAL tree, mostly various topology Python packages, and also mess with the Jupyter(-Lab) config. So that I can debug, what's a specific command that results in an error?

— Reply to this email directly, view it on GitHub https://github.com/3-manifolds/sagedocker/issues/2#issuecomment-1142143095, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJ6CP3PT6X7G6CUGFVYH6DVMYILDANCNFSM5WJC6JAA . You are receiving this because you are subscribed to this thread.Message ID: @.***>