[MacPorts] #59822: cmake @3.16.1: error: no matching constructor for initialization of 'const std::vector<ExpectedSpec>'

[MacPorts]

#59822: cmake @3.16.1: error: no matching constructor for initialization of 'const
std::vector<ExpectedSpec>'
----------------------+------------------------------------
  Reporter:  letaage  |      Owner:  michaelld
      Type:  defect   |     Status:  assigned
  Priority:  High     |  Milestone:
 Component:  ports    |    Version:  2.6.2
Resolution:           |   Keywords:  mountainlion mavericks
      Port:  cmake    |
----------------------+------------------------------------
Changes (by Ionic):

 * cc: Ionic (added)


Comment:

 I think so, yes. Newer `llvm` versions use `cmake` as their built system
 so blacklisting a version that is used as a bootstrap compiler will lead
 to a dead end. Maybe the loop thing was wrong, I don't remember.

 I haven't followed this stuff very actively, though, jeremyhu probably
 knows much better. It also mostly concerns really, really, really old
 operating systems that do not feature `libc++` or `C++11` support out of
 the box and hence need to bootstrap with old `llvm`/`clang` versions in
 order to get a newer one.

 I'll see if a very simple patch gets `cmake` going again on my 10.9
 system. That would be great. No promises though.

 > Related to using an already-installed cmake to build a newer one [...]

 Yep, that makes build unreproducible, including the issue of not knowing
 whether old versions can be used to correctly bootstrap the package. I
 also don't know how that would pan out in trace mode, because sometimes
 trace mode doesn't seem to hide the files completely, but merely deny read
 or write access to them, so such a check would still come out `true`, but
 subsequent uses fail.

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