[MacPorts] #65895: clang-15: port compilation failure tracking

MacPorts noreply at macports.org
Sat Sep 24 23:46:13 UTC 2022

#65895: clang-15: port compilation failure tracking
  Reporter:  mascguy   |      Owner:  cjones051073
      Type:  defect    |     Status:  assigned
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:  2.7.2
Resolution:            |   Keywords:  clang-15
      Port:  inkscape  |

Comment (by kencu):

 inkscape is actually wrong here, and clang-15 is right. gcc-12 currently
 still allows std::unary_function, but not for long, as it’s announcing it


 I have been going through this for many years, as 10.6.8 has traditionally
 always used the newest clang, and with every new compiler release, things
 get tighter and codebase errors show up. I also asked a few years ago if
 we could hang back a few cycles on updating compilers, and leave the work
 to others — I don’t have to tell you what the response to that request was


 So for many years I found and fixed these nearly daily as those on newer
 systems using older clangs cruised merrily by.

 We can use this (defaulting to clang-15 on some systems) as a good method
 to help upstream keep their codebase correct… macports has traditionally
 done that frequently.

 If you’re taking on too many ports as maintainer, just ease off a bit. You
 went from zero to about 1000 in six months :)

 The crash with darktable now is something different… but I don’t think
 anyone ever opened up an issue with llvm, so it will not be fixed until
 they know about it.

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

More information about the macports-tickets mailing list