[MacPorts] #60150: portgroups cargo, cargo-fetch fail to build new port topgrade

MacPorts noreply at macports.org
Wed Mar 25 07:20:29 UTC 2020


#60150: portgroups cargo, cargo-fetch fail to build new port topgrade
-----------------------+---------------------------------
  Reporter:  lhaeger   |      Owner:  MarcusCalhoun-Lopez
      Type:  defect    |     Status:  assigned
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:  2.6.2
Resolution:            |   Keywords:
      Port:  topgrade  |
-----------------------+---------------------------------

Comment (by kencu):

 you probably cannot fix this by configuring your build. If it's like the
 other examples we've seen of this, it has to do with clang using modules
 and mixing this up. We could disable screen extras in our ncurses build,
 but that's felt to be imperfect. We could edit the unctrl.h header and
 tweak in a fix, but that's inelegant. We bumped this upstream to Apple a
 few weeks back.

 Until that gets sorted out someday, you're DOA on MacPorts ( homebrew
 apparently doesn't see this error, at least it is only reported on
 MacPorts and never there, possibly as they install headers into /usr/local
 and that's on the default search path.)

 So, after you dig a bit, if it is modules causing the error, you won't be
 able to use MacPorts until it gets resolved. You can edit a quick hack
 into your own version of /opt/local/include/unctrl.h to fix it for
 yourself ( that's what I did ) pending either us tweaking ours in our
 ncurses build formally (unlikely) or App fixing modules (will happen, no
 idea when). Or perhaps the MacPorts decision to leave this will turn if it
 affects enough people, hard to say...

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


More information about the macports-tickets mailing list