[Slackbuilds-users] Sage build still broken?

[King Beowulf]

On 03/10/2018 12:43 AM, Duncan Roe wrote:
> On Sun, Feb 25, 2018 at 10:59:25AM -0800, King Beowulf wrote:
>> On 02/25/2018 08:44 AM, JCA wrote:
>>> 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
>>>
>> ---snip----
>>>
>>>    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.
>>>
>>
>> I feel your pain, and I do not have a workable solution yet.  Sage
>> upstream is completely hostile to relocatable packages it seems...  The
>> core problem is in how the sage devs have designed their build system.
>>
>--snip--
>>
> Hey Ed,
> 
> SBo has mkchroot which was put together to solve this kind of problem,
> 
> Cheers ... Duncan.

Thanks.  I was hoping to avoid that since upstream now has a way to
generate a 'relocate.py' script to compile a git branch that I can't
seem to get to work. Guess I'll give up and try mkchroot.

-Ed


-------------- 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/20180310/a3ea21d8/attachment.asc>