@rgommers Should we update vendored-meson as well. I've been conservative about that.

@r-devulap I assume that there is a missing backport here. Do you know what it is?

EDIT: I may just omit this backport, it was a maybe yes, maybe no decision to try.

probably this one? #26338

@rgommers Should we update vendored-meson as well. I've been conservative about that.

Working on it at numpy/meson#15

Working on it at

I suspect the new risc failure may be meson connected.

There is a failure on the riscv qemu build @r-devulap does this ring a bell?

FAILED: numpy/_core/libhighway.a.p/src_highway_hwy_targets.cc.o 
c++ -Inumpy/_core/libhighway.a.p -Inumpy/_core -I../numpy/_core -I../numpy/_core/src/highway -I/numpy/build/meson_cpu -fdiagnostics-color=always -D_GLIBCXX_ASSERTIONS=1 -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=c++17 -O2 -g -fPIC -DTOOLCHAIN_MISS_ASM_HWCAP_H -MD -MQ numpy/_core/libhighway.a.p/src_highway_hwy_targets.cc.o -MF numpy/_core/libhighway.a.p/src_highway_hwy_targets.cc.o.d -o numpy/_core/libhighway.a.p/src_highway_hwy_targets.cc.o -c ../numpy/_core/src/highway/hwy/targets.cc
../numpy/_core/src/highway/hwy/targets.cc: Assembler messages:
../numpy/_core/src/highway/hwy/targets.cc:631: Error: unrecognized opcode `vsetvli s0,zero,e8,m1,ta,ma'

@mattip I think you need to backport this PR #26273 as well. The changes in numpy/_core/meson.build seem relevant.

I think you need to backport this PR #26273 as well.

Looking at the diff of numpy/_core/meson.build, there seem to be a few other missing pieces as well. Is the problem fixed by #26797 also present in 2.0.0? If not, I'm inclined to skip this backport, it is getting overly intrusive.

Looking at the diff of numpy/_core/meson.build, there seem to be a few other missing pieces as well. Is the problem fixed by #26797 also present in 2.0.0? If not, I'm inclined to skip this backport, it is getting overly intrusive.

unfortunately, yes :( The original bug report was for numpy 2.0.0