Hello,
The following commands seem to produce a binary package that can be
relocated:
0. make distclean
1. make all-build
2. make doc
3. . local/bin/sage-env
4. ./local/bin/sage-bdist
The package in dist appears to be relocateable, but further testing is
required!
Of course, the official solution is probably better.
Regards,
Kapil.
--
On Monday, 29 February 2016 15:17:22 UTC+5:30, Kapil Paranjape wrote:
>
> Hello,
>
> Sage (from sage-7.0.tar.gz) was built from source with the following
> commands:
>
> $ export MAKE="make -j16 -l19"
> $ export SAGE_FAT_BINARY="yes"
> $ make
> $ ./sage -i pyopenssl
> $ ./sage -i beautifulsoup
> $ ./sage --bdist
>
> The resulting dist/sage-7.0-x86_64-Linux.tar.gz was copied elsewhere.
>
> The .tar.gz was unpacked in this different location. Running './sage' from
> this location gave the following error:
>
> ERROR: The Sage installation tree has moved
>
> from /home/kapil/sage-7.0
> to /home/kapil/test/sage-7.0-x86_64-Linux
>
> This is not supported, and Sage will not work. To install Sage from a
> binary package:
>
> 1. Open the .tar.bz2 archive (or .dmg on OSX)
>
> 2. Move the SageMath folder/app to where you want it to be. You can
> also rename the directory now.
>
> 3. Start sage for the first time. This will then automatically patch
> paths in binaries.
>
> After starting Sage for the first time you cannot change the
> installation any more. To install Sage elsewhere, start over from the
> binary package. Or recompile Sage from scratch in the new location
> ("make distclean && make)
>
> Further investigation revealed that as the message above says sage is no
> longer relocatable.
>
> So on to the questions:
>
> 1. Why does "sage --bdist" still exist if if does not work? At the
> very least it should give a message saying something like "Unpack in
> *exactly* the same location where you built Sage" *and* sage -bdist should
> not name the top-level directory incorrectly (as it currently does).
> 2. The installation instructions (README.txt e.g.) should probably
> indicate the above and stop suggesting "sage -bdist" perhaps?
> 3. What is the solution available for people who want to install Sage
> in a container of some kind (e.g. chroot) where all the build-tools are
> not
> available or there is not enough space to build sage and the existing
> binaries do not work (incompatible libc for example)?
>
> Thanks in advance for suggestions,
>
> Kapil.
> --
>
>
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.
