[MacPorts] #57092: wxgtk-3.0: build fails on 10.12 (shared-ld: unhandled option '-stdlib=libc++')

[MacPorts]

#57092: wxgtk-3.0: build fails on 10.12 (shared-ld: unhandled option
'-stdlib=libc++')
------------------------+----------------------
  Reporter:  jwhowse4   |      Owner:  mojca
      Type:  defect     |     Status:  assigned
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:
Resolution:             |   Keywords:
      Port:  wxgtk-3.0  |
------------------------+----------------------

Comment (by kencu):

 I get the same error, building it on 10.6.8 configured with libc++:
 {{{
 CXX="/opt/local/bin/clang++-mp-3.9"
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_wxWidgets-3.0/wxgtk-3.0/work/wxWidgets-3.0.4/build
 /shared-ld-sh -bundle -headerpad_max_install_names -o
 webkit2_extu30.bundle webkit2_ext_webview_webkit2_extension.o
 -L/opt/local/lib -Wl,-headerpad_max_install_names -stdlib=libc++ -arch
 x86_64  -L/opt/local/lib  -framework IOKit -framework CoreServices
 -framework System -framework ApplicationServices   -L/opt/local/lib
 -lwebkit2gtk-4.0 -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0
 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lsoup-2.4 -lgio-2.0
 -ljavascriptcoregtk-4.0 -lgobject-2.0 -lglib-2.0 -lintl -Wl,-framework
 -Wl,CoreFoundation -lz -lpthread -liconv
 shared-ld: unhandled option '-stdlib=libc++'
 make: *** [webkit2_extu30.bundle] Error 1
 }}}
 the script that errors out is this one:
 {{{
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_wxWidgets-3.0/wxgtk-3.0/work/wxWidgets-3.0.4/build
 /shared-ld-sh
 }}}
 and in that script, the `-stdlib=libc++` option is not handled. I added
 some script manually to handle that flag like this:
 {{{
        -stdlib*)
         # collect these options
         args="${args} $1"
         ;;
 }}}
 and then it worked fine, and the port installed.

 The trick is how to patch that functionality into the port so it doesn't
 need to be done manually. It would be easy enough to generate a patch, and
 then manually add that patch with a `system` call in the portfile.

 Ideally, we'd figure out how to add it to the configure.in script (where I
 believe this is generated).

 THAT is not so easy for me...

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