[MacPorts] #71739: wxgtk-3.0 @3.0.5.1_4+x11: build fails on 10.7: error: no member named 'auto_ptr' in namespace 'std'

[MacPorts]

#71739: wxgtk-3.0 @3.0.5.1_4+x11: build fails on 10.7: error: no member named
'auto_ptr' in namespace 'std'
------------------------+----------------------
  Reporter:  kencu      |      Owner:  mojca
      Type:  defect     |     Status:  reopened
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:
Resolution:             |   Keywords:  lion
      Port:  wxgtk-3.0  |
------------------------+----------------------
Changes (by kencu):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 I reverted this commit because it wasn't quite right ... so now it's just
 as broken as it was two days ago :>

 The issues:

 1. the default compilers for some MacOS versions build as c++17, and this
 code doesn't build as c++17 or newer at present. IMHO the c++ standards
 should be set to what the code calls for. Other options might include
 hacking the code to build as c++17 for no particular purpose, or
 restricting compilers to those that default to pre-c++17 standards.
 2. some of the wx-30 ports that are marked as not being c++11
 possibly/probably have been building as c++11 (or other) on some systems
 with compilers that default in certain ways. This is messy, and not
 deterministic. Some users eagerly want this to continue. Dealer's choice.
 3. The portfile is unwieldly, and IMO need a re-make. The last commit I
 did was wrong, in part due to my not noticing certain things, but in
 larger part to the way the portfile is currently laid out.
 4. I suspect that some of the patches, esp the latest few, are not needed.
 Barracuda pushed a patch, opened an issue upstream, and then (as far as I
 can tell) concluded he had made a symlink of some kind that was then gone
 and couldn't repo the error that led to the patch that is currently in
 macports now. Dunno about that ,  no time to go back and check it.
 5. The wxgtk +quartz variant is marked as non-functional, but is there.
 6. The wxgtk-3.0-cxx11 subort is building as x11, but is not marked as
 such in it's variants.

 So -- a big cleanup is required to get back to normalcy.

 I might have taken this on, taken over maintainership, and fixed this mess
 all up but -- TBH, I just don't feel like arguing with barracuda about
 every single point all the time.

 So -- have at.

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