[MacPorts] #69990: cmake-bootstrap fails to link on 10.4 due to changes in ncurses 6.5.0

MacPorts noreply at macports.org
Fri May 17 16:13:27 UTC 2024


#69990: cmake-bootstrap fails to link on 10.4 due to changes in ncurses 6.5.0
------------------------------+--------------------
  Reporter:  miles-martin-66  |      Owner:  (none)
      Type:  defect           |     Status:  new
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:
Resolution:                   |   Keywords:  tiger
      Port:  cmake-bootstrap  |
------------------------------+--------------------

Comment (by kencu):

 I tried a few simple workarounds...

 setting {{{-DNCURSES_OPAQUE=0}}} actually doesn't work out, as the
 macports curses header overrides it anyway unless other, less palatable,
 defines are also set.

 I tried forcing {{{compiler.cpath /usr}}} on Tiger -- but I was both
 disappointed and surprised that didn't work either.

 We could copy the system curses.h into a folder and set that as an include
 folder to be used ahead of others, but hacks like that often come back to
 bite you later. Still, that is on the easy side.

 Or we (someone we) could figure out where {{{${prefix}/include}}} is being
 added to the default include path for the gcc compilers, fix that, and
 then revbump the compiler.  I checked, and gcc7 on TIger (at least) does
 the same search order, and so I suspect all the gcc compilers do that --
 and they should probably all not do that any longer :> Now there is a
 project for a hearty individual to take on.

 We could also change the newer ncurses 6.5.0 to use {{{NCURSES_OPAQUE=0}}}
 by default again, at least on systems where it is needed to be so (where
 the system curses library apparently doesn't have the accessor functions
 to make OPAQUE=1 work). That is Josh's port, and I'm not getting involved
 in suggesting changes to ncurses that will almost certainly get shot down
 anyway.

 Of all these options -- I guess copying the system curses.h  into a folder
 in the build tree and prioritizing that include folder is the easiest.

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


More information about the macports-tickets mailing list