[MacPorts] #61511: wireshark3 @3.4.0_0+cares+chmodbpf+geoip+gnutls+kerberos5+libsmi+python37+qt5+zlib: error: use of undeclared identifier 'CLOCK_REALTIME'

[MacPorts]

#61511: wireshark3
@3.4.0_0+cares+chmodbpf+geoip+gnutls+kerberos5+libsmi+python37+qt5+zlib:
error: use of undeclared identifier 'CLOCK_REALTIME'
-------------------------+----------------------------------
  Reporter:  thetrial    |      Owner:  ghosthound
      Type:  defect      |     Status:  accepted
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.6.4
Resolution:              |   Keywords:  legacy-os, elcapitan
      Port:  wireshark3  |
-------------------------+----------------------------------

Comment (by mascguy):

 After doing more build testing with a simpler patch - and re-encountering
 the build error related to QT 5.9 - I realized that the wireshark version
 is now at 3.4.2. Duh, right?

 In any case, after pondering this for a few weeks, these are my
 recommendations:

 For the immediate term: To ensure our users have access to wireshark3 for
 older macOS releases, update the port to gracefully fallback to 3.4.1 [for
 those cases]. That will stop the bleeding, and provide said users with a
 working port. This should probably be done ASAP.

 Longer-term: If we want to support the latest wireshark3 releases across-
 the-board, there's going to be some work involved. Either we'll need to
 get QT 5.9 working for older macOS versions, or patch wireshark3 to not
 require QT 5.9 components. (I don't know whether the latter is even
 practical - or feasible - but throwing it out there as an idea.) Someone
 should also check the cmake scripts, and see if the project has a flag to
 disable the user of newer QT components. That sounds too good to be true,
 but who knows.

 Thoughts?

-- 
Ticket URL: <https://trac.macports.org/ticket/61511#comment:26>
MacPorts <https://www.macports.org/>
Ports system for macOS