<div dir="ltr">For the record I tried on the 3 GB RAM/1 GB swap, 64-bit 14.2 system, this time without X, and it built correctly. It would seem that, at least in my two systems, having X/XFCE running when trying to build this version of sage is a no-no.</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 27, 2017 at 12:36 AM, Christoph Willing <span dir="ltr"><<a href="mailto:chris.willing@iinet.net.au" target="_blank">chris.willing@iinet.net.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 27/03/17 13:53, Christoph Willing wrote:<br>
> On 27/03/17 12:52, Willy Sudiarto Raharjo wrote:<br>
>> I tried on yet another system, again 64-bit 14.2, this time with 6 GB RAM<br>
>>> and 3 GB swap, running XFCE but nothing else, and I am getting the same<br>
>>> result. I'll try again, this time without X running.<br>
>><br>
>> Just to make sure to run a complete installation of Slackware{64}-14.2<br>
>> with the latest patch is preferred.<br>
>><br>
>> Notes:<br>
>> my last build of sage was in March 9, so i haven't tried it again since then<br>
>><br>
><br>
> I just built 7.5.1 (March 9 update) in a full x86_64 14.2 VM without any<br>
> problems.<br>
><br>
> However on installation, the running of sage (from doinst.sh) fails with<br>
> "ERROR: The Sage installation tree has moved" error - full message<br>
> attached. The same message is shown when running sage from the command<br>
> line.<br>
><br>
</span>I made a new build which commented out running of sage from doinst.sh.<br>
<br>
According to the /opt/sage/sage script, running it the first time runs<br>
relocate-once.py and then deletes it. I wanted to look at<br>
relocate-once.py before it was deleted so had to stop sage being run by<br>
doinst.sh. The new build and installation went well - sage didn't run.<br>
However relocate-once.py still wasn't in SAGE_ROOT as expected - I can't<br>
find it in the sage package that was installed either.<br>
<br>
In fact I couldn't see relocate-once.py in the source tarball either so<br>
I presume it should be generated at build time. Since it's not in the<br>
final package, I'm guessing that it hasn't been generated. That would<br>
explain the error message about not being able to run after being relocated.<br>
<br>
chris<br>
<br>
<br>
<br>______________________________<wbr>_________________<br>
SlackBuilds-users mailing list<br>
<a href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.<wbr>org</a><br>
<a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" rel="noreferrer" target="_blank">http://lists.slackbuilds.org/<wbr>mailman/listinfo/slackbuilds-<wbr>users</a><br>
Archives - <a href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/" rel="noreferrer" target="_blank">https://lists.slackbuilds.org/<wbr>pipermail/slackbuilds-users/</a><br>
FAQ - <a href="https://slackbuilds.org/faq/" rel="noreferrer" target="_blank">https://slackbuilds.org/faq/</a><br>
<br>
<br></blockquote></div><br></div>