On Sun, Feb 20, 2022 at 04:32:43PM -0500, Jeremy Bicha wrote: > On Sun, Feb 20, 2022 at 1:46 PM Adam Borowski <kilob...@angband.pl> wrote: > > The correct answer currently is: > > [amd64 arm64 armhf i386 mips64el mipsel ppc64el s390x powerpc ppc64] > > but it keeps changing, and you don't want to track it by hand if I can do > > that for you. > > > > Thus: please [b-]depend on valgrind-if-available.
> Do you have any suggestions on how to handle this when the valgrind > test is set by a configure flag? Is the configure flag required to enable valgrind tests? If not, the very point of "configure" scripts is to auto-detect presence of tools. > The way I've been handling it is to just keep a hard-coded list of > valgrind architectures in sync between my debian/control and > debian/rules. if which valgrind >/dev/null; then Meow! -- ⢀⣴⠾⠻⢶⣦⠀ We domesticated dogs 36000 years ago; together we chased ⣾⠁⢠⠒⠀⣿⡁ animals, hung out and licked or scratched our private parts. ⢿⡄⠘⠷⠚⠋⠀ Cats domesticated us 9500 years ago, and immediately we got ⠈⠳⣄⠀⠀⠀⠀ agriculture, towns then cities. -- whitroth on /.
