[Slackbuilds-users] Sage build still broken?

JCA 1.41421 at gmail.com
Sun Feb 25 16:44:53 UTC 2018


I built Sage 8.0 as available to Slackware 14.2 using the relevant sbopkg
queue.  The build process closes as follows:

RROR:  The Sage installation tree has moved

from /tmp/SBo/sage-8.0
  to /opt/sage

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")

Package sage-8.0-x86_64-1_SBo.tgz installed.


Done upgrading/installing package.

+++++++++++++++++++++++++++++++++++++++++++
SUMMARY LOG
Using the SBo repository for Slackware 14.2
Queue Process:  Download, build, and install

sage:
  MD5SUM check for sage-8.0.tar.gz ... OK
  Building package sage-8.0-x86_64-1_SBo.tgz ... OK
  Installing package sage-8.0-x86_64-1_SBo.tgz ... OK

+++++++++++++++++++++++++++++++++++++++++++

###########################################
          Queue process complete!
###########################################

   When trying to use it, this is what I am getting:

$ sage
************************************************************************
It seems that you are attempting to run Sage from an unpacked source
tarball, but you have not compiled it yet (or maybe the build has not
finished). You should run `make` in the Sage root directory first.
If you did not intend to build Sage from source, you should download
a binary tarball instead. Read README.txt for more information.
************************************************************************

   This in a freshly installed 14.2 system, with 24G RAM and 1TB disk
space. The compilation was completed normally, ending up with 13GB worth of
files in /tmp/SBo, and more than 5GB in /opt/sage.

   What have I done wrong? If nothing, is there any point in keeping Sage
in Slackbuilds? Even in a beefy system, compiling Sage takes a several
hours - and ending up with lots of GBs eaten up in your hard drive and a
nonfunctional application is frustrating.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180225/c1f0c0f8/attachment-0001.html>


More information about the SlackBuilds-users mailing list