This has been a problem for a bit now. In another thread
<https://groups.google.com/d/msg/sage-support/Tv68G0h8Keg/WB85DLVMBgAJ>
from the summer, I noted that a common workaround is to set
export OPENBLAS_CONFIGURE="TARGET=ATOM"
I don't quite know about how the updates to openBlas might affect this from
now on, though.
On Thursday, November 9, 2017 at 6:45:04 PM UTC, Andy Howell wrote:
>
> I'm running under Ubuntu 17.10, which is in a VM under under VirtualBox.
>
> OpenBlas is complaining that it can't work out the CPU type.
> /proc/cpuinfo shows it as:
>
> Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
>
> I think that might have already been addressed with an update version of
> openBlas
>
> https://trac.sagemath.org/ticket/23272
>
> If someone can help with git commands to pull that into to the dev
> branch I can give it a try.
>
> I tried installing openBlas 0.2.20 dev libs from the distribution, but
> it was not used in the build.
>
> Thanks,
>
> Andy
>
--
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
