Re: [sage-devel] Re: Error Building on Slackware 14.2

2020-06-10 Thread Matthias Koeppe
On Wednesday, June 10, 2020 at 10:30:10 AM UTC-7, Christopher Duston wrote: > > I am interested in helping with this - I just want to be clear because I > don't have much experience with containers. > It's easy to start by just taking an existing Dockerfile (that tox.ini generates) and adding st

Re: [sage-devel] Re: Error Building on Slackware 14.2

2020-06-10 Thread Christopher Duston
I am interested in helping with this - I just want to be clear because I don't have much experience with containers. If we add an entry to the tox.ini corresponding to slackware-14.2-multilib, it would allow for the automatic testing of Sage in that OS? I have gone through the portability wiki, so

Re: [sage-devel] Re: Error Building on Slackware 14.2

2020-06-04 Thread Matthias Koeppe
Thanks. I have created https://trac.sagemath.org/ticket/29798 for adding a slackware-multilib test environment to our tox.ini. Would you be interested in helping with this? See https://doc.sagemath.org/html/en/developer/portability_testing.html for an overview. On Thursday, June 4, 2020 at 3:0

Re: [sage-devel] Re: Error Building on Slackware 14.2

2020-06-04 Thread Christopher Duston
Thanks, I appreciate the attention. Instructions for making Slackware multilib can be found here: https://docs.slackware.com/slackware:multilib. "Quick and Dirty" instructions are about 20% of the way down. I should note that multilib is not officially supported by either Slackware or Slackbuilds

Re: [sage-devel] Re: Error Building on Slackware 14.2

2020-06-04 Thread Matthias Koeppe
Thanks. I have created https://trac.sagemath.org/ticket/29795 for this issue. Could you advise how to create a multilib slackware configuration? On Thursday, June 4, 2020 at 11:42:49 AM UTC-7, Christopher Duston wrote: > > I'd like to follow up on this - the real issue is that when building iml

Re: [sage-devel] Re: Error Building on Slackware 14.2

2020-06-04 Thread Christopher Duston
I'd like to follow up on this - the real issue is that when building iml the libraries are hardcoded to reside at /lib, but in multilib systems this may not be the case. Specifically, in Slackware we have lib for 32-bit and lib64 for 64-bit. I fixed this by changing this line in build/pkgs/iml/ spk

Re: [sage-devel] Re: Error Building on Slackware 14.2

2020-03-19 Thread Matthias Koeppe
Thanks. I have recreated a similar configuration (slackware-14.2-standard - https://trac.sagemath.org/ticket/29354), but cannot seem to reproduce the error. iml installs correctly for me. Looking at your log files, these lines look rather suspicious: /usr/lib64/gcc/x86_64-slackware-linux/5.5.0

Re: [sage-devel] Re: Error Building on Slackware 14.2

2020-03-18 Thread Christopher Duston
I ran those two commands, and piped the output to a file, attached here. Thanks. On Tue, Mar 17, 2020 at 5:53 PM Matthias Koeppe wrote: > On Tuesday, March 17, 2020 at 3:56:49 PM UTC-4, Christopher Duston wrote: >> >> I've got an error when compiling SageMath 9.0 from source on a Slackware >> 1

Re: [sage-devel] Re: Error Building on Slackware 14.2

2020-03-17 Thread Matthias Koeppe
OK, please try this: slackpkg generate-template d; cat /etc/slackpkg/templates/d.template On Tuesday, March 17, 2020 at 5:18:50 PM UTC-4, Christopher Duston wrote: > > Of course: > > # slackpkg generate-template > slackpkg - version 2.82.1 > > Usage: > slackpkg [OPTIONS] {install|remove|search|

Re: [sage-devel] Re: Error Building on Slackware 14.2

2020-03-17 Thread Christopher Duston
Of course: # slackpkg generate-template slackpkg - version 2.82.1 Usage: slackpkg [OPTIONS] {install|remove|search|file-search| upgrade|reinstall|blacklist} {PATTERN|FILE} slackpkg [OPTIONS] {generate-template|install-template|remove-template} TEMPLATENAME slackpkg [OPTIONS] info PACKAGE sla

Re: [sage-devel] Re: Error Building on Slackware 14.2

2020-03-17 Thread Matthias Koeppe
Thanks. And the output of "slackpkg generate-template" please if that works for you On Tuesday, March 17, 2020 at 4:19:53 PM UTC-4, Christopher Duston wrote: > > Attached - sorry about that. > > On Tue, Mar 17, 2020 at 4:11 PM Matthias Koeppe > wrote: > >> Please post the top-level config.log to