[MacPorts] #65778: libfilezilla @0.32.0: link fails for 10.7 thru 10.12: undefined symbols for std::bad_variant_access

[MacPorts]

#65778: libfilezilla @0.32.0: link fails for 10.7 thru 10.12: undefined symbols for
std::bad_variant_access
---------------------+--------------------------
 Reporter:  mascguy  |      Owner:  mascguy
     Type:  defect   |     Status:  assigned
 Priority:  Normal   |  Milestone:
Component:  ports    |    Version:  2.7.2
 Keywords:           |       Port:  libfilezilla
---------------------+--------------------------
 Details:

 {{{
 Undefined symbols for architecture x86_64:
   "typeinfo for std::bad_variant_access", referenced from:
       std::__1::__throw_bad_variant_access() in libfilezilla_la-json.o
   "vtable for std::bad_variant_access", referenced from:
       std::__1::__throw_bad_variant_access() in libfilezilla_la-json.o
   NOTE: a missing vtable usually means the first non-inline virtual member
 function has no definition.
 ld: symbol(s) not found for architecture x86_64
 }}}

 https://ports.macports.org/port/libfilezilla/details/

 Based on the logs, it looks like the cxx standard is properly set to 2017
 during compilation. And 2017-compliant compilers are also being requested
 by the port.

 Would this be fixable via `macports-libcxx`? Or is there a preferred
 fix...?

-- 
Ticket URL: <https://trac.macports.org/ticket/65778>
MacPorts <https://www.macports.org/>
Ports system for macOS