On Wed, 4 Dec 2019 at 17:51, mmarco wrote:
> Thanks, using
>
> OPENBLAS_CONFIGURE="TARGET=ZEN" make
>
> seemed to work.
>
> Now, since It will be running a patchbot, it might need to recompile
> openblas depending on the ticket that is being checked at each time. Is
> there a way to make sure th
Great, now fflas_ffpack complains about not finding blas
--
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 view this disc
Thanks, using
OPENBLAS_CONFIGURE="TARGET=ZEN" make
seemed to work.
Now, since It will be running a patchbot, it might need to recompile
openblas depending on the ticket that is being checked at each time. Is
there a way to make sure that this flag is used always?
El miércoles, 4 de diciembr
I suppose openblas fails to recongnise the CPU, resorts to TARGET=ATOM
and fails there.
You probaby can try setting OPENBLAS_CONFIGURE="$OPENBLAS_CONFIGURE TARGET=???"
replacing ??? with the correct value, and rebuild...
On Wed, Dec 4, 2019 at 4:09 PM mmarco wrote:
>
> I am trying to setup severa
