[MacPorts] #70002: weechat @4.2.2: Looking for include file ncurses.h - not found

MacPorts noreply at macports.org
Thu May 16 21:19:53 UTC 2024


#70002: weechat @4.2.2: Looking for include file ncurses.h - not found
---------------------------+---------------------------
  Reporter:  drwhitehouse  |      Owner:  cardi
      Type:  defect        |     Status:  assigned
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.9.3
Resolution:                |   Keywords:  tiger leopard
      Port:  weechat       |
---------------------------+---------------------------

Comment (by ryandesign):

 Replying to [comment:9 drwhitehouse]:
 > I have two questions:
 >
 > {{{
 > port select --set gcc mp-gcc
 > }}}
 >
 > It sounds like I need to undo this setting, I think it was set to "none"
 before - is that right?

 Your use of `port select` should not interfere with how ports build. It
 sometimes does, and when it does that's a bug to be fixed. In this case,
 selecting gcc won't interfere, because we can see that the compiler is
 being used by its full correct path `/usr/bin/g++-4.2`. Problem only arise
 when ports build using a generic compiler name like `g++` since that's
 what `port select gcc` changes.

 > Secondly (I apologise) can you confirm this is the file to comment out
 those two lines:
 >
 >
 /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/irc/weechat/work/weechat-4.2.2/CMakeLists.txt
 >
 > I believe its lines 36/37.

 That should be it.
 /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/irc/weechat/work
 is a symlink to
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_irc_weechat/weechat/work
 so the actual path of that file on disk is
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_irc_weechat/weechat/work/weechat-4.2.2/CMakeLists.txt.

 > I tried that (I think) and got the same error if I recall correctly, so
 I'm not convinced it did anything!
 > However I've cleaned up a couple of times since then.

 cmake may cache things. It may be enough to delete the file
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_irc_weechat/weechat/work/build/CMakeCache.txt
 after changing CMakeLists.txt and before trying to install again.

 Alternately, start from a clean slate with `sudo port clean weechat` and
 `sudo port extract weechat`, then make the change to CMakeLists.txt, then
 `sudo port install weechat`.

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


More information about the macports-tickets mailing list