valgrind-macos-devel: error: Valgrind works on Darwin 10.x-20.x (Mac OS X 10.6-10.11 and macOS 10.12-11.0)

[sudheerhebbale (Sudheer Hebbale)]

After upgrade macos Monterey version 12.0.1

Build of valgrind-macos-devel fails due to error in configuration

Valgrind works on Darwin 10.x-20.x (Mac OS X 10.6-10.11 and macOS 10.12-11.0)

[ryandesign (Ryan Carsten Schmidt)]

The error message is pretty clear:

checking for a supported OS... ok (darwin21.1.0)
checking for the kernel version... unsupported (21.1.0)
configure: error: Valgrind works on Darwin 10.x-20.x (Mac OS X 10.6-10.11 and macOS 10.12-11.0)

So we need to upgrade to a newer version of this software that is compatible with macOS 12, or if none exists, the developers need to create it first; in that case, you might contact them about it.

[Ranguvar (Devin Cofer)]

Per Valgrind dev Paul Floyd's comment, Valgrind may need to be patched in MacPorts for this. Still, there may be more issues.

​https://stackoverflow.com/questions/69792467/memory-check-on-macos-12-monterey

[barracuda156]

Valgrind is also broken for PPC, despite allegedly supporting 10.5.

This is on Rosetta:

checking build system type... powerpc-apple-darwin10
checking host system type... powerpc-apple-darwin10
checking for a supported CPU... ok (powerpc)
checking for a 64-bit only build... no
checking for a 32-bit only build... yes
checking for a supported OS... ok (darwin10)
checking for the kernel version... Darwin 10.x (10.8.0) / Mac OS X 10.6 Snow Leopard
checking for a supported CPU/OS combination... no (ppc32-darwin)
configure: error: Valgrind is platform specific. Sorry. Please consider doing a port.

[raimue (Rainer Müller)]

PR: ​https://github.com/macports/macports-ports/pull/21395

[raimue (Rainer Müller)]

In 28ceab79c0914d404bd37ac6ded3a6e4ff1c49f5/macports-ports (master):

valgrind-macos-devel: Update to 3.22.0-r2023-10-29

Closes: #63792