[Slackbuilds-users] trying to fix sage-8.1 build script - advice needed

King Beowulf kingbeowulf at gmail.com
Mon Jan 8 04:01:45 UTC 2018

On 01/07/2018 05:10 PM, Willy Sudiarto Raharjo wrote:
>> I'm attempting to upgrade and fix a few issue with the sage build.
>> However, upstream seems to think that no one wants to compile a
>> redistributable install package.  The way sage works is:
>> 1. Download prebuilt binary, extract it somewhere, rename directory if
>> desired, set a few shell variables, symlink, run.  Once run and the
>> binaries patched, you can't move it.
>> 2. Download source, compile somewhere, AND DON'T MOVE IT!
>> In other words, upstream does not support moving to a new directory
>> after compiling.  SAGEROOT seems to get hard coded.  Thus, our normal
>> procedure of building in /tmp/SBo/sage-x.y.z creates binaries that can
>> only be run from /tmp/SBo/sage-x.y.z and moving the tree to /opt/sage
>> results in an error message
>> ERROR: The Sage installation tree has moved
>> from /tmp/SBO/sage-8,1
>>   to /opt/sage
>> stating that you cannot move the compiled tree to a new location -
>> either use prebuilt binaries or recompile.
>> Now, the question is: How does upstream create relocatable binaries?
>> What is the patch process?
>> Otherwise, we will have to compile in /opt/sage and then create a
>> package from that tree location.
> During my time as a maintainer for sage, it does built everything into
> /tmp/SBo/sage-xx and then during installation, it would move everything
> from /tmp/SBo to /op/sage because the script in doinst.sh will do so.
> I have tested the installation and it worked fine.
> I don't know about 8.1 because i haven't tried it yet

That's what I thought as well and it worked for 8.0. 8.1 seems to hard
code all SAGEROOT everywhere.  Running from doinst.sh as root to have
sage reset the paths no longer works.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180107/16288cec/attachment-0001.asc>

More information about the SlackBuilds-users mailing list