[MacPorts] #58677: legacy support issue while building cmake (Leopard)

[MacPorts]

#58677: legacy support issue while building cmake (Leopard)
-----------------------+---------------------------------
  Reporter:  rmottola  |      Owner:  (none)
      Type:  defect    |     Status:  new
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:
Resolution:            |   Keywords:  leopard i386 legacy
      Port:  cmake     |
-----------------------+---------------------------------

Comment (by kencu):

 Things are really in flux just now -- MacPorts 2.6 is coming out any day
 now, and everything is going to change on Intel systems 10.6 to 10.8 very
 shortly. So there is some distraction due to that.

 Very few people use a Mac 10.5 Intel system, so you're kind of a niche
 (but important) user base there.

 My plan, once the dust settles, is to try to sell the idea to treat 10.5
 Intel like 10.6 Intel (once I get clang-8.0 actually building on 10.5
 Intel). That will be the easiest solution. Then 10.5 intel will also
 default to libc++, just like 10.6 Intel will be doing, and these wacky
 (and irritating) inconsistencies between gcc and clang and the libgcc
 headers and the libc++ headers will mostly GO AWAY! Problem solved.

 We will see how long 10.4 and 10.5 PPC support lasts with gcc and libgcc.
 Maybe a while, if I can keep it quiet and under the radar without too many
 tickets showing up about it. If there is too much hassle, the drumbeat is
 getting louder and louder to just cut support and be done with it. We'll
 see...it will happen sooner or later.

 For right now -- the next month or so -- please force cmake to build
 against libc++ on 10.5 Intel as you did above, and then you should be OK
 pending the eventual fallout that is coming from the MP 2.6 rollout.

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