can work with the
SAGE engineers to help make this happen. It all follows a pattern, and
design decisions can be made.
I will go and read what was written in trac.
On Thursday, March 7, 2019 at 2:39:09 AM UTC-6, Dima Pasechnik wrote:
>
> On Thu, Mar 7, 2019 at 7:54 AM Ike Stoddard &
What about --with-blas=atlas configure argument? Where is that consumed?
I believe ./configure is at fault. Specifying atlas is detected in
configure:7054 line
but by line 9050 it is forgotten. Despite specifying it, atlas was built!
"sage_spkg_install_openblas" has been set to "no" but is not re
THANK YOU!
On Mon, Mar 4, 2019 at 09:58 E. Madison Bray wrote:
> On Mon, Mar 4, 2019 at 11:34 AM Ike Stoddard
> wrote:
> >
> > But why not ATLAS? Should I look at the numpy makefile?
>
> I have reported this before as https://trac.sagemath.org/ticket/20507
>
&
ge = f77
>
> FOUND:
> libraries = ['openblas', 'lapack', 'openblas', 'blas']
> library_dirs = ['/usr/local/src/Misc/sage-8.6/local/lib', '/usr/lib64']
> define_macros = [('NO_ATLAS_INFO', 1), ('HAVE
Numpy log and sagelib log were attached to original note.
On Sun, Mar 3, 2019 at 15:32 François Bissey wrote:
> I need more info for a diagnostic. Logs and more logs.
>
> > On 4/03/2019, at 10:09, Ike Stoddard wrote:
> >
> > Relevantly, numpy build process does not fi
ings like in sage.
>
> > On 3/03/2019, at 19:16, Ike Stoddard > wrote:
> >
> > Linux xxx 4.20.12-arch1-1-ARCH #1 SMP PREEMPT Sat Feb 23 15:11:34
> UTC 2019 x86_64 GNU/Linux
> >
> > Building from source; make fails at sagelib, but implies "numpy"
the version above to another
> you need to rebuild all packages linking to libgfortran. That means
> anything that uses lapack and in particular numpy when compiled with
> lapack bindings like in sage.
>
> > On 3/03/2019, at 19:16, Ike Stoddard wrote:
> >
> > Linux xxx
Check disks for space?
On Sun, Feb 24, 2019 at 12:42 Paul Clarke wrote:
> Hello,
> Sage failed during compilation of the gfortran component. It appears that
> the files were compiled successfully, but there was an error when copying
> them to their final destination.
>
> Here is the error messag
appropriate people to ask are the arch maintainers for the package
> not this mailing list.
>
> Sorry.
>
> > On 21/02/2019, at 20:29, Dima Pasechnik wrote:
> >
> > On Thu, Feb 21, 2019 at 6:25 AM Ike Stoddard
> wrote:
> >>
> >> 1) I have instal
1) I have installed atlas-lapack-base as blas/lapack for a number of
packages already.
2) sagemath tries to install its own blas/lapack (openblas)
3) is there a way to configure sagemath to use this library instead?
Otherwise I am in uninstall/reinstall hell.
pacman -S sagemath
resolving depende
ild normally with SPKG_CHECK
> * build breaks at linbox.
> * Do a one shot install of linbox
> * resume build with make until the next issue.
>
> > On 21/02/2019, at 17:13, Ike Stoddard
> wrote:
> >
> > But will this work without a prior installation?
> >
> &g
But will this work without a prior installation?
On Wed, Feb 20, 2019 at 19:00 François Bissey wrote:
> ./sage -i linbox
>
> > On 21/02/2019, at 13:51, Ike Stoddard
> wrote:
> >
> > Unfortunately, I cannot see how to do that. How do I install a one-shot?
> &g
Unfortunately, I cannot see how to do that. How do I install a one-shot?
In the unpacked linbox subtree: spkg-install? src/linbox-auto-install?
On Wednesday, February 20, 2019 at 1:51:33 PM UTC-6, François Bissey wrote:
>
> sage is not yet able to use a system installed linbox.
> You could insta
d OpenCL with Sage's linbox...
>
> On Wed, Feb 20, 2019 at 6:26 PM Ike Stoddard
> wrote:
> >
> > test-opencl-domain failed to compile. Log is attached.
> >
> >
> > Host system:
> > Linux Light1DAW 4
Yep. Wanted to check subsystems before putting package together.
On Wed, Feb 20, 2019, 13:24 Dima Pasechnik You are running with SAGE_CHECK=yes, isn't it?
> Anyhow, I don't think anyone tried OpenCL with Sage's linbox...
>
> On Wed, Feb 20, 2019 at 6:26 PM Ike Stoddar
15 matches
Mail list logo
