sysdig: build on Linux

[carlocab]

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• 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?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

Let's see if this builds with minimal workarounds first.

[carlocab]

Ok, I think I've tried all the suggestions from #84990 and then some. @danielnachun @cho-m any ideas here?

[cho-m]

Current error is happening in Protobuf-generated C header, but I am not sure of exact reason:

/tmp/sysdig-20211019-18237-b1mrls/sysdig-0.27.1/build/userspace/libsinsp/cri.pb.h:2883:53: error: expected unqualified-id before numeric constant
 2883 |   const ::runtime::v1alpha2::LinuxPodSandboxConfig& linux() const;
      |                                                     ^~~~~

It might be the same problem Arch hit when trying to use C++17 standard, which is mentioned in the same upstream issue:

I tried building sysdig with c++17 as well, patching the cmake files where necessary, but it fails with a different type of error with the code generated by protobuf, I think. I don't have the log handy at the moment, but I can try it again and paste it here later if you need it.

Can try dropping C++17 changes and see if it works even though there is different C++ standard between abseil and sysdig.

[carlocab]

Suggested change

# We need C++17 to use Abseil.

Oops. I'll remove this when merging...