Valgrind cavheat highsierra

[MartinDelille]

• Have you followed the guidelines for contributing?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing brew install <formula>)?

---

I simply added a cavheat information for 10.13 users.

[SMillerDev]

Why does valgrind require HEAD with High Sierra?

[MartinDelille]

Because current valgrind release don't support it. More information here:

• brew install valgrind fails but new version is available #23536
• https://www.gungorbudak.com/blog/2018/04/28/how-to-install-valgrind-on-macos-high-sierra/

Changing the repository URL doesn't seems to be necessary.

[SMillerDev]

Afaik as a rule homebrew doesn't suggest using the head option of a formula as it requires compiling everything on the machine. @ilovezfs any opinions?

[ilovezfs]

Upstream should do a release. Has anyone asked for one? Given how close macOS Mojave is to release, and the current stable version of valgrind is not High Sierra compatible, we're nearing deletion territory for the formula at this point.

[MartinDelille]

I will ask.

[MartinDelille]

Done: https://bugs.kde.org/show_bug.cgi?id=383811#c26

[Echelon9]

Valgrind's upstream MacOS maintainer here.
Preliminary work is being undertaken to prepare for Valgrind's next numbered release. Unfortunately I don't have a specific date that I can communicate, but it is in train.
Appreciate this might not be the immediate answer you wanted -- but thought best to get it out there.
Thanks for the interest.

[SMillerDev]

Will that release work on mojave? Or no idea about that yet?

[Echelon9]

Very unlikely to have Mojave support in any Valgrind release (other than git Valgrind) at the time of Mojave's public release.

The issue we face is that Valgrind needs to tie fairly closely into the mach kernel syscalls. And these are added to/changed each major macOS release. And we can't release the Valgrind code supporting any changes until the public release of macOS version "n" happens, as otherwise we're breaching the pre-release T&Cs.

We've been fairly good at get rudimentary macOS "n" support into git versions within a month or so of public release, but it's not reasonable to expect the prior Valgrind numbered release will support the new macOS version ahead of time.
Does that help with guidance?

[fxcoudert]

Thanks for suggesting the caveat @MartinDelille.
Given the information given by upstream, I think we'll decline the caveat: we typically don't suggest building from head, and hopefully a new release is here soon!