[MacPorts] #52931: kismet: install failure on 10.8.5, slightly different from ticket 36486 (was: Kismet install failure on 10.8.5, slightly different from ticket 36486)

[MacPorts]

#52931: kismet: install failure on 10.8.5, slightly different from ticket 36486
------------------------------+----------------------
  Reporter:  TheLastLovemark  |      Owner:  mascguy
      Type:  defect           |     Status:  assigned
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:  2.3.5
Resolution:                   |   Keywords:
      Port:  kismet           |
------------------------------+----------------------
Changes (by mascguy):

 * cc: evanmiller (added)
 * port:  Kismet => kismet


Comment:

 While this is a very old ticket - for a much earlier version of `kismet`,
 with different issues - I figured we might as well repurpose this to track
 work to expand where this port builds.

 With the latest commit, it now builds for 10.11 and later:

 https://github.com/macports/macports-
 ports/commit/b7fa94563a0ef81f40987c9caaaac8212f03a159

 For 10.10 and earlier, there are failures related to use of `NSArray`.
 Presumably these are newer additions for that component, which weren't
 present way back:

 {{{
 capture_osx_corewlan_wifi.m:64:38: error: expected '>'
 @property (retain) NSArray<CWChannel *> *channels;
                                      ^
 capture_osx_corewlan_wifi.m:64:39: error: expected member name or ';'
 after declaration specifiers
 @property (retain) NSArray<CWChannel *> *channels;
                    ~~~~~~~            ^
 capture_osx_corewlan_wifi.m:64:1: error: property requires fields to be
 named
 @property (retain) NSArray<CWChannel *> *channels;
 ^                  ~~~~~~~~~~~~~~~~~~~
 capture_osx_corewlan_wifi.m:64:39: error: expected ';' at end of
 declaration list
 @property (retain) NSArray<CWChannel *> *channels;
                                       ^
                                       ;
 }}}

 The port has been updated to require Cxx17, so I don't think (?) that's
 the issue. But still digging.

 If anyone has any thoughts, let me know.

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