[Slackbuilds-users] Sage build still broken?

Didier Spaier didier at slint.fr
Sun Feb 25 19:02:20 UTC 2018


Le 25/02/2018 à 17:44, JCA a écrit :
>    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.

As it happens I have compiled (but not pacakaged) sage-8.1 15 days ago, just to check for a bind friend where the pdf were stored when e.g. drawing a sphere.

I just unpacked  a git archive then ran:

tar xf sage-8.1.tar.gz 
cd sage-8.1
./configure | tee /tmp/config.LOG
time make 2>/tmp/sageERR |tee /tmp/sageLOG

I attach config.LOG but not sageLOG, too heavy (25M), but here is hw it ends:

>Testing that Sage starts...
>[2018-02-06 23:26:22] SageMath version 8.1, Release Date: 2017-12-07
>This looks like the first time you are running Sage.
>Cleaning up, do not interrupt this.
>Done cleaning.
>Yes, Sage starts.
>make[2] : on quitte le répertoire « /tmp/sage-8.1/build/make »
>make[1] : on quitte le répertoire « /tmp/sage-8.1/build/make »
>real	257m49.177s
>user	262m42.133s
>sys	11m29.261s
>Sage build/upgrade complete!
>To install small scripts to directly run Sage's versions of GAP,
>the PARI/GP interpreter, Maxima, or Singular etc. (by typing e.g.
>just 'gap' or 'gp') into a standard 'bin' directory, start Sage
>by typing 'sage' (or './sage') and enter something like
>    install_scripts('/usr/local/bin')
>at the Sage command prompt ('sage:').

My laptop didn't burn this time...

didier[/tmp]$ du -sh sage-8.1/
7,7G	sage-8.1/

It worked here, that's all I know.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.LOG
Type: text/x-log
Size: 9637 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180225/9da7c816/attachment.bin>

More information about the SlackBuilds-users mailing list