py38-numpy, py37-numpy, py36-numpy, py35-numpy, py27-numpy: Library not loaded: /opt/local/lib/libopenblas-r1.dylib

[ryandesign (Ryan Carsten Schmidt)]

py36-scipy fails to build:

​https://build.macports.org/builders/ports-10.15_x86_64-builder/builds/163675/steps/install-port/logs/stdio

Traceback (most recent call last):
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/numpy/core/__init__.py", line 22, in <module>
    from . import multiarray
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/numpy/core/multiarray.py", line 12, in <module>
    from . import overrides
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/numpy/core/overrides.py", line 7, in <module>
    from numpy.core._multiarray_umath import (
ImportError: dlopen(/opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/numpy/core/_multiarray_umath.cpython-36m-darwin.so, 2): Library not loaded: /opt/local/lib/libopenblas-r1.dylib
  Referenced from: /opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/numpy/core/_multiarray_umath.cpython-36m-darwin.so
  Reason: image not found

This was caused by switching the OpenBLAS port to using cmake. It no longer provides /opt/local/lib/libopenblas-r1.dylib.

[catap (Kirill A. Korinsky)]

A simple rebuild of py-numpy should fix that issue, and as far as I recall I've bump that revision as well.

[erikbs]

Replying to catap:

A simple rebuild of py-numpy should fix that issue, and as far as I recall I've bump that revision as well.

py311-numpy was rebuilt ln my system because of the rev-bump. It appeared to build just fine, but when I try to import it, it complains about missing symbols in OpenBLAS (_xerbla_). nm -gU reveals that NumPy is right – there is no such symbol in the OpenBLAS dylib anymore.

Since NumPy does not work, e.g. SciPy does not work either.

[ryandesign (Ryan Carsten Schmidt)]

Replying to catap:

A simple rebuild of py-numpy should fix that issue, and as far as I recall I've bump that revision as well.

[7882fbb52b86a91d92dc20d7916155bff6ed9d7f/macports-ports] only revbumped py39-numpy and later. It did not revbump py38-numpy or earlier.

[erikbs]

Replying to ryandesign:

Replying to catap:

A simple rebuild of py-numpy should fix that issue, and as far as I recall I've bump that revision as well.

[7882fbb52b86a91d92dc20d7916155bff6ed9d7f/macports-ports] only revbumped py39-numpy and later. It did not revbump py38-numpy or earlier.

Got it. Then I will create a separate bug report for py311-scipy/py311-numpy/_xerblas_

[catap (Kirill A. Korinsky)]

Replying to ryandesign:

Replying to catap:

A simple rebuild of py-numpy should fix that issue, and as far as I recall I've bump that revision as well.

[7882fbb52b86a91d92dc20d7916155bff6ed9d7f/macports-ports] only revbumped py39-numpy and later. It did not revbump py38-numpy or earlier.

ah, sorry for missed that.

[barracuda156]

All pythons prior to 3.9 affected: #68816

[ryandesign (Ryan Carsten Schmidt)]

I mentioned that in comment:4.

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #68879. Is something standing in the way of revbumping the remaining py-numpy subports? They've been broken for two weeks.

[barracuda156]

In 7800bd904376c43300d4b1e19a2e9018e75fc554/macports-ports (master):

py-numpy: update to 1.26.2, unbreak older versions

Fixes: #68807
See also: #68908