[MacPorts] #68283: mas @1.8.6: error: conflicting types for 'unctrl' (was: Unable to build on M1 running Sonoma: "Invalid manifest")

[MacPorts]

#68283: mas     @1.8.6: error: conflicting types for 'unctrl'
------------------------+--------------------------
  Reporter:  dancamper  |      Owner:  kimuraw
      Type:  defect     |     Status:  assigned
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.8.1
Resolution:             |   Keywords:  sonoma arm64
      Port:  mas        |
------------------------+--------------------------
Changes (by ryandesign):

 * status:  new => assigned
 * cc: judaew (added)
 * keywords:   => sonoma arm64
 * version:   => 2.8.1
 * owner:  (none) => kimuraw


Comment:

 I think the relevant portion of the log is more likely to be:

 {{{
 <module-includes>:488:9: note: in file included from <module-
 includes>:488:
 #import "curses.h"
         ^
 /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.sdk/usr/include/curses.h:2054:10:
 note: in file included from
 /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.sdk/usr/include/curses.h:2054:
 #include <unctrl.h>
          ^
 /opt/local/include/unctrl.h:61:54: error: conflicting types for 'unctrl'
 NCURSES_EXPORT(NCURSES_CONST char *) NCURSES_SP_NAME(unctrl) (SCREEN*,
 chtype);
                                                      ^
 /opt/local/include/unctrl.h:58:38: note: previous declaration is here
 NCURSES_EXPORT(NCURSES_CONST char *) unctrl (chtype);
                                      ^
 }}}

 There seems to be some confusion where the macOS curses header is
 including a MacPorts ncurses header; that's unlikely to work well.

 The appearance of the phrase "module-includes" here makes me think of
 #68149 but I don't know if it's actually related.

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