[MacPorts] #69374: gcc13 optimizer bug in ncurses

[MacPorts]

#69374: gcc13 optimizer bug in ncurses
---------------------------+--------------------
  Reporter:  ThomasDickey  |      Owner:  (none)
      Type:  defect        |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:
Resolution:                |   Keywords:
      Port:  gcc13         |
---------------------------+--------------------

Comment (by ryandesign):

 Replying to [comment:3 ThomasDickey]:
 >> (in case there's some way to mark the port as conflicting with gcc13).

 Replying to [comment:4 kencu]:
 > macports can do that, yes.
 >
 > It can mark gcc13 as an unusable compiler for that port.

 Well a port can indicate, using `compiler.blacklist`, that MacPorts should
 not choose some compiler(s) to build it. However, I don't see why MacPorts
 would ever have chosen gcc13 for ncurses to begin with. Since the port
 doesn't contain any directives to the contrary, MacPorts should have
 chosen clang.

 Was ncurses built with gcc13 because you explicitly asked to build it with
 gcc13 (e.g. `sudo port -s install ncurses configure.compiler=macports-
 gcc-13`, which is not recommended)? If so, then MacPorts doesn't currently
 have a way to prevent that. Command-line compiler selections override
 `compiler.blacklist`.

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