[MacPorts] #61498: dialog @1.3: configure: error: No curses header-files found

[MacPorts]

#61498: dialog @1.3: configure: error: No curses header-files found
----------------------+-----------------------------
  Reporter:  pejaham  |      Owner:  ryandesign
      Type:  defect   |     Status:  accepted
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:  2.6.4
Resolution:           |   Keywords:  catalina bigsur
      Port:  dialog   |
----------------------+-----------------------------

Comment (by iay):

 Although it shows up as the configure step failing to detect a curses
 header file such as {{{<ncurses.h>}}} (which does in fact exist in the
 right place if the dependency has been installed), the actual problem here
 is that configure detects header files by attempting to compile sample
 programs, and those are failing to compile: configure just sees the
 failure and misattributes it.

 It looks like in many cases this is because the test program that
 configure is using to detect the appropriate header file references a
 function(e.g.,  {{{tgoto}}}) that is not defined there but in a different
 header, thus hitting the {{{implicit declaration of function 'tgoto' is
 invalid in C99}}} error.

 The definitions for the code that generates those test programs seems to
 live in {{{aclocal.m4}}} but my understanding of the whole C configuration
 stack is way too thin to have much chance of making progress beyond that.

 Having said which, I did find https://dickey.his.com/autoconf/my-
 autoconf/CHANGES.html#t20210103 which seems to address exactly this thing:

 >* AcSplit/CF_NCURSES_CONFIG, AcSplit/CF_NCURSES_LIBS:
 >change compile-check from tgoto to tigetstr, because tgoto is not
 prototyped
 >in ncurses' curses.h while tigetstr is prototyped.  Lacking the prototype
 >can cause the configure check to fail with a recent clang configuration
 on
 >macOS, which turn on -Werror=implicit-function-declaration by default
 >(report by Dennis Preiser)

 That's dated 2021-01-03 (just a few days ago) so something may be
 happening upstream. I'm not sure ''where,'' though.

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