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
My build says halswell
perl ./gensymbol osx x86_64 _ 1 0 0 0 0 0 "" "" 1 > osx.def
gcc -O2 -DMAX_STACK_ALLOC=2048 -DEXPRECISION -m128bit-long-double -Wall -m64
-DF_INTERFACE_GFORT -fPIC -DNO_WARMUP -DMAX_CPU_NUMBER=4 -DASMNAME=_
-DASMFNAME=__ -DNAME=_ -DCNAME= -DCHAR_NAME=\"_\" -DCHAR_CNAME=\"\"
It might be hardware specific; I take it you don't have a sandy bridge CPU?
On Tuesday, April 11, 2017 at 12:19:26 AM UTC+2, John H Palmieri wrote:
>
> I ran Xcode to make sure it would update any component pieces and then ran
> a build from scratch. Openblas built just fine for me (same Xcode
I ran Xcode to make sure it would update any component pieces and then ran
a build from scratch. Openblas built just fine for me (same Xcode version).
John
On Monday, April 10, 2017 at 3:00:19 PM UTC-7, François wrote:
>
> I may need to try a build from scratch, takes time (to build gcc mainl
This is now https://trac.sagemath.org/ticket/22794
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group,
When I build with "sage -p openblas" then I end up with this
error: https://github.com/xianyi/OpenBLAS/issues/942
I'm not sure why I don't get the same error,
but https://github.com/xianyi/OpenBLAS/pull/982 fixes it for me...
On Tuesday, April 11, 2017 at 12:00:19 AM UTC+2, François wrote:
>
I may need to try a build from scratch, takes time (to build gcc mainly).
François
> On 11/04/2017, at 09:58, Volker Braun wrote:
>
> Yes, same here:
>
> osx:~ vbraun$ xcode-select -v
> xcode-select version 2347.
>
>
> I'm pretty sure its the xcode update, it failed during the weekly full
>
Yes, same here:
osx:~ vbraun$ xcode-select -v
xcode-select version 2347.
I'm pretty sure its the xcode update, it failed during the weekly full
rebuild and we didn't change anything on openblas last week
On Monday, April 10, 2017 at 11:57:18 PM UTC+2, François wrote:
>
> I don’t seem to b
I don’t seem to be able to reproduce the problem. I have Xcode 8.3.1 and
Mirage:~ fbissey$ xcode-select -v
xcode-select version 2347.
Are you at the same level?
François
> On 11/04/2017, at 08:03, Francois Bissey
> wrote:
>
> It makes shifting to clang a bit more urgent. I will look into tha
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
Having issues building the same package. Only I get a different log file. I
always prefer building Sage from scratch for performance, but have lately
been having trouble doing so, as Sage keeps failing to build. Background:
OS: Debian 8.7, 64-bit.
Sage Version: 7.6.
HW: Lenovo ThinkPad 11e, 120G
It makes shifting to clang a bit more urgent. I will look into that particular
fault
ASAP.
François
> On 11/04/2017, at 07:58, Volker Braun wrote:
>
> The most recent Xcode update seems to have broken openblas on the OSX
> buildbot. Build log errors start at:
>
>
>
> gcc -c -O2 -DMAX_STACK
The most recent Xcode update seems to have broken openblas on the OSX
buildbot. Build log errors start at:
gcc -c -O2 -DMAX_STACK_ALLOC=2048 -DEXPRECISION -m128bit-long-double -Wall
-m64 -DF_INTERFACE_GFORT -fPIC -DNO_WARMUP -DMAX_CPU_NUMBER=8 -DASMNAME=_
-DASMFNAME=__ -DNAME=_ -DCNAME= -DCHA
15 matches
Mail list logo
