Hi Zachary,
You might be hitting https://github.com/xianyi/OpenBLAS/issues/2728 which
is fixed in https://github.com/xianyi/OpenBLAS/pull/2729 but not in 0.3.10.
Isuru
On Mon, Oct 12, 2020 at 10:01 PM Zachary Scherr wrote:
> Hi Isuru,
>
>I've been trying to fix homebrew's openblas, and I'm
Hi Isuru,
I've been trying to fix homebrew's openblas, and I'm running into an
issue that I was hoping you might know something about. If I build
openBLAS with TARGET=HASWELL then I don't have any issues with numpy.
However, if I build it with TARGET=NEHALEM, which is what they want for
h
Ah, thank you. I'll post the issue and see if I can get homebrew to
resolve it!
On Monday, October 12, 2020 at 2:29:10 PM UTC-4 isu...@gmail.com wrote:
> You don't need different TARGETs. `DYNAMIC_ARCH=1` means that it will
> detect at runtime what the CPU is and will use the kernel matching t
You don't need different TARGETs. `DYNAMIC_ARCH=1` means that it will
detect at runtime what the CPU is and will use the kernel matching the CPU
at runtime. `TARGET` gives the oldest CPU that this code will run on so
that the common code is compiled to target this.
Isuru
On Mon, Oct 12, 2020 at 1
I posted about it on their discussion page, but I'm not sure there will be
anything they can do. They build their libraries on several different
versions of MacOS, but I'm not sure they build with several different
TARGETS. I can try to pursue this, but the easy fix for now is that if
people
On Mon, Oct 12, 2020 at 6:17 PM Isuru Fernando wrote:
>
> I looked at the openblas formula in homebrew and they are not passing the
> TARGET option. When using DYNAMIC_ARCH=1, a target should be specified.
care to open an issue with them on https://github.com/Homebrew/homebrew-core ?
>
> Isuru
Aha. In fact, if I do
brew install openblas --build-from-source
then it picks up the TARGET automatically and I don't have any problems
with numpy whatsoever. I'll still ask over there, but I'm guessing this is
the problem with trying to use bottled versions of the libraries.
On Monday, Octob
I looked at the openblas formula in homebrew and they are not passing the
TARGET option. When using DYNAMIC_ARCH=1, a target should be specified.
Isuru
On Mon, Oct 12, 2020 at 11:34 AM Zachary Scherr wrote:
> In case anyone is curious, I've tracked the problem down to homebrew's
> openBLAS and
In case anyone is curious, I've tracked the problem down to homebrew's
openBLAS and so it has nothing to do with sage. If I build numpy from
source through homebrew then I get exactly the same error using my system
python3. I'm wondering if maybe this has something to do with the fact
that op
On 10/12/20 4:52 AM, Samuel Lelièvre wrote:
2020-10-12 04:12 UTC, Raymond Rogers:
On 10/11/20 7:12 PM, Samuel Lelievre wrote:
2020-10-11 22:12:20 UTC, Raymond Rogers:
Jupyter didn't run because of "openssl development" missing.
This mate release doesn't have openssl-dev stand alone.
I did hav
Attached is a jupyter notebook that runs Sage 9.1, a (slightly more)
minimal example of a problem that I discovered. When calculating the
determinant of a large (in the sense n>=9 I have currently found) symbolic
matrix the answer is not correct. To see this, run the notebook with
Qsimplify eit
2020-10-12 04:12 UTC, Raymond Rogers:
>
> On 10/11/20 7:12 PM, Samuel Lelievre wrote:
> >
> > 2020-10-11 22:12:20 UTC, Raymond Rogers:
> > >
> > > Jupyter didn't run because of "openssl development" missing.
> > > This mate release doesn't have openssl-dev stand alone.
> > > I did have openssl inst
12 matches
Mail list logo
