Re: Build warning with meson and dtrace on Fedora 43

Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com> writes:
> Hi, Laurenz!
> Thanks for the report. I tried to fix the patch in the attachment.

BF animals caiman, midge, tayra, timberworm are all complaining about
this. In keeping with meson's general habit of verbose yet largely
useless configuration reporting, it's impossible to tell exactly what
OS versions those are running, though their possibly-outdated BF
metadata claims recent Red Hat versions. However, I also reproduced
the warning with an autoconf build on current Fedora 43 / x86_64.

> Commits ca326e903d and 1f8c504e308 widened the byte-count arguments of
> smgr__md__read__done and smgr__md__write__done to "long long int".
> SystemTap's dtrace(1) pyparsing grammar rejects that multi-word type and
> falls back with a warning (misreported near the previous probe). Use
> "long" instead, which matches ssize_t on our LP64 DTrace platforms and
> is already used elsewhere in probes.d.

This seems to me to be a fundamentally broken, hence short-lived
workaround. I think we need another way. As you mention upthread,
we document that system-header types such as ssize_t should not be
used in probes.d because "they cause compilation errors on macOS".
But I tried it just now and it compiles fine on current Tahoe.
Maybe that note is obsolete?

regards, tom lane