>From a bash shell where you build Sage:
export OPENBLAS_CONFIGURE="TARGET=ATOM" MAKE="make -j5 -l3.5"
should set the important variables. This is the MAKE I use for a very, very
old 4 core machine. The OPENBLAS_CONFIGURE variable is alluded to
in build/pkgs/openblas/spkg-check but I find it no
All right! Sage 7.6 compiled correctly, so far as I know. I haven't run the
tests, but it opens into a notebook in Firefox, and correctly computes
integrate(e^(-x^2),x,-infinity,infinity)
Is there a way to combine the OPENBLAS_CONFIGURE command with the -j4
option for using multiple cores to co
7.5.1 failed to build. Looks like the same error as before. I'll try
Steven's linked suggestion with 7.6, and see if that flies.
Thanks for all your help, by the way!
One suggestion: if the OPENBLAS_CONFIGURE="TARGET=ATOM" make command builds
everything correctly, then maybe the next version
It is curious that 7.5.1 would build but not 7.6. You might get some
mileage with
OPENBLAS_CONFIGURE="TARGET=ATOM" make
See this thread:
https://groups.google.com/forum/#!topic/sage-release/3QJoAgg9bgo
On Monday, April 10, 2017 at 8:00:51 PM UTC-5, Ackbach wrote:
>
> I'm afraid I don't have t
OK 7.5.1 and 7.6 have the same version of openblas, so something else changed
to cause the build failure.
So, yes try to build 7.5.1 again. If it fails now, the cause is likely a change
in
the host system. If it succeeds that’s probably something else in sage that
changed.
> On 11/04/2017, at 1
I'm afraid I don't have that data. I will say I've never been able to
compile Sage 7.6 the first time. I have definitely been able to compile
7.5.1 and earlier the first time, though sometimes there are still errors.
I can try to compile 7.5.1 on this machine and get back to you how it works.
O
Did it start happening with openblas 0.2.19 or did it suddenly happen
one release build openblas 0.2.19 successfully and the next didn’t?
I suspect it is a CPU detection problem, we have seen similar logs
before on atom chips.
François
> On 11/04/2017, at 07:45, Ackbach wrote:
>
> Having issues
Wasn't stated in the build instructions.
On Thursday, October 13, 2016 at 5:03:20 AM UTC-4, François wrote:
>
> Not spending the time compiling gcc to get gfortran?
>
> François
>
> > On 13/10/2016, at 22:01, Sébastien Labbé >
> wrote:
> >
> >
> >
> > On Wednesday, October 12, 2016 at 9:07:
On 2016-10-13 11:31, Sébastien Labbé wrote:
Is there a page in the Sage wiki or Sage documentation about "How to
install Sage from source faster" that gathers all those tricks?
This page is the best I can think of:
http://doc.sagemath.org/html/en/installation/source.html
For example, how do I
Is there a page in the Sage wiki or Sage documentation about "How to
install Sage from source faster" that gathers all those tricks?
The only thing I currently use is parallel stuff : export MAKE = "make -j4"
For example, how do I know that the architecture of my dual core os x
laptop is CoreDu
Not spending the time compiling gcc to get gfortran?
François
> On 13/10/2016, at 22:01, Sébastien Labbé wrote:
>
>
>
> On Wednesday, October 12, 2016 at 9:07:24 PM UTC+2, Eric Gourgoulhon wrote:
> > with Ubuntu 16.04, if you install the Ubuntu package gfortran-5, your Sage
> > build will us
11 matches
Mail list logo
