BLD: Update vendor-meson to fix module_feature conflicts arguments bug#28635
Conversation
54a6976 to
4f767a7
Compare
|
@rgommers Is the meson update OK? |
Yes that's on purpose here. Once CI is green here, numpy/meson#12 can be merged and this PR updated to include the |
|
The failure looks meson related. Caching? Or maybe the submodule needs an update. |
That's true, the submodule (the pr hash) needs a rebase current armhf error:numpy/_core/tests/test_memmap.py . [ 0%] numpy/_core/tests/test_multiarray.py ................................... [ 0%] ....................................................s................... [ 0%] ............................................XX.......................... [ 0%] .Fatal Python error: AbortedCurrent thread 0x41007020 (most recent call first): Extension modules: numpy._core._multiarray_umath, numpy.linalg._umath_linalg, numpy._core._multiarray_tests, numpy._core._rational_tests, numpy._core._umath_tests, cython.cimports.libc.math, numpy.random._common, numpy.random.bit_generator, numpy.random._bounded_integers, numpy.random._mt19937, numpy.random.mtrand, numpy.random._philox, numpy.random._pcg64, numpy.random._sfc64, numpy.random._generator, numpy._core._struct_ufunc_tests, numpy._core._simd, numpy._core._operand_flag_tests, numpy.linalg.lapack_lite (total: 19) close/open, re-test we have native armhf support now. |
176ec5b to
26074af
Compare
26074af to
4f767a7
Compare
4f767a7 to
1cb8aa1
Compare
Fix incorrect handling of the compiler arguments 'conflicts' that was causing failures when detecting asmid instructions at compile time on aarch32 platforms.
1cb8aa1 to
1d261ff
Compare

Bug detected and fixed by @Vogtinator in PR numpy/meson#12. The issue was located in the Meson features module, and implementing the fix will require updating the vendored Meson repository.