You may also try
https://github.com/sagemath/binary-pkg
to rewrite paths etc. We used to build binary packages using this tool,
packages you can install into any prefix.
No ./configure options would help you here.
It's actually less remapping hassle to use as many system packages as possible.
The Sage distribution does not support relocation after build and also not
DESTDIR-style staged installation.
See https://github.com/sagemath/sage/issues/36860#issuecomment-1854730246
for the suggested method for downstream packaging of Sage.
On Saturday, December 23, 2023 at 10:13:49 AM UTC-8
Ugh sorry my mistake, that's the error when running /opt/sage. The error
when running from SAGE_LOCAL/bin/sage is
$ pwd
/tmp/SBo/package-sage/INSTALL/bin
$ ./sage
./sage: ././sage-config: /tmp/SBo/package-sage/INSTALL/bin/python3: bad
interpreter: No such file or directory
./sage: ././sage-config:
Hello,
I am the maintainer for the Slackware package of SageMath. They've
recently instituted a policy that all packages must be built in /tmp, which
makes things tricky with Sage, as the build directory might get removed at
a later point, and Sage needs that. Previously I had just built
