Meson: update of dependency results in linker error

[tobiasdiez]

I've upgraded system m4ri, and now get a weird linking error:

$ ldd build/cp313/src/sage/rings/polynomial/pbori/pbori.cpython-313-x86_64-linux-gnu.so
	linux-vdso.so.1 (0x00007fe32f0c1000)
	libbrial.so.3 => /usr/lib64/libbrial.so.3 (0x00007fe32eedf000)
	libbrial_groebner.so.3 => /usr/lib64/libbrial_groebner.so.3 (0x00007fe32ea00000)
	libm4ri.so.1 => /usr/lib64/libm4ri.so.1 (0x00007fe32eead000)
	libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/15/libstdc++.so.6 (0x00007fe32e600000)
	libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/15/libgcc_s.so.1 (0x00007fe32ee7e000)
	libc.so.6 => /usr/lib64/libc.so.6 (0x00007fe32e411000)
	libm.so.6 => /usr/lib64/libm.so.6 (0x00007fe32ed95000)
	libm4ri-0.0.20200125.so => not found
	libpng16.so.16 => /usr/lib64/libpng16.so.16 (0x00007fe32ed5c000)
	libgomp.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/15/libgomp.so.1 (0x00007fe32e9a8000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fe32f0c3000)
	libz.so.1 => /usr/lib64/libz.so.1 (0x00007fe32ed3f000)

so it seems that the Cython/gcc compilation result for pbory.pyx is cached somewhere, so it has to be purged, but how?

Originally posted by @dimpase in #39973 (comment)

It should be clarified in the docs how to deal with this error. Namely, calling meson setup --wipe <builddir>.

[dimpase]

is meson setup --wipe <builddir> more than rm -rf <builddir> ?

[tobiasdiez]

Slightly - it restores some config/ini files afterwards.