Ask Your Question

# Revision history [back]

### After debugging problem in building Sage library during initial build, how to continue?

Suppose you are building Sage, and an error comes up. Usually, in most spkgs, if there is something that needs to be changed in the code of the spkg, you can cd into the spkg/build/ directory for the package, go into src/, fix the error (if you have any idea what it is, of course!) in the source, and then continue the spkg-install from there.

This is not the case in the Sage library spkg sage-x.y.z. itself, though. You have to do something else. I am trying to figure out what that is! I was once shown, but have forgotten. I've tried $SAGE_ROOT/sage -b, $SAGE_ROOT/sage -ba, and ./spkg-install. I didn't really expect the first two to work, given that they would operate on the already copied files (not the ones in the build directory), but the latter also doesn't seem to work.

I remember having this exact problem, and cannot remember what to do. Help!

 2 retagged FrédéricC 4078 ●3 ●37 ●84

### After debugging problem in building Sage library during initial build, how to continue?

Suppose you are building Sage, and an error comes up. Usually, in most spkgs, if there is something that needs to be changed in the code of the spkg, you can cd into the spkg/build/ directory for the package, go into src/, fix the error (if you have any idea what it is, of course!) in the source, and then continue the spkg-install from there.

This is not the case in the Sage library spkg sage-x.y.z. itself, though. You have to do something else. I am trying to figure out what that is! I was once shown, but have forgotten. I've tried $SAGE_ROOT/sage -b, $SAGE_ROOT/sage -ba, and ./spkg-install. I didn't really expect the first two to work, given that they would operate on the already copied files (not the ones in the build directory), but the latter also doesn't seem to work.

I remember having this exact problem, and cannot remember what to do. Help!