On Monday, February 29, 2016 at 10:47:22 AM UTC+1, Kapil Paranjape wrote: > > > 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? > > Agreed. Patches are welcome...
> 1. 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)? > > Build a relocatable binary using https://github.com/sagemath/binary-pkg -- 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 sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
