[Bug 206471] sysutils/tmux USES=ncurses seems to be a no-op

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Fri Jul 1 06:04:42 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206471

Chris Hutchinson <portmaster at bsdforge.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |portmaster at bsdforge.com

--- Comment #1 from Chris Hutchinson <portmaster at bsdforge.com> ---
(In reply to Vick Khera from comment #0)
> A while ago I reported a bug I observed using the sysutils/tmux program in
> bug #193685
> 
> The TL;DR is that I needed tmux to be linked using the ports ncurses rather
> than the system ncurses to avoid display errors in certain circumstances.
> 
> Fast forward to today (well, a while ago, but I cannot pinpoint exactly
> when) it seems that the build of tmux is registering a dependency on the
> ports ncurses package, but is not actually linking against it. This used to
> work, but some update between the original bug fix and now causes it to not
> link to the ports ncurses. Perhaps it is that I'm running FreeBSD 10.2 now?
> 
> This is what I see:
> 
> [root at lorax]# ldd /usr/local/bin/tmux
> /usr/local/bin/tmux:
> 	libutil.so.9 => /lib/libutil.so.9 (0x80088c000)
> 	libncurses.so.8 => /lib/libncurses.so.8 (0x800a9e000)
> 	libevent-2.0.so.5 => /usr/local/lib/libevent-2.0.so.5 (0x800ceb000)
> 	libulog.so.0 => /lib/libulog.so.0 (0x800f2e000)
> 	libc.so.7 => /lib/libc.so.7 (0x801130000)
> 	libthr.so.3 => /lib/libthr.so.3 (0x8014dc000)
> 	libmd.so.6 => /lib/libmd.so.6 (0x801700000)
> [root at lorax]# pkg info -dr tmux
> tmux-2.1_1
> Depends on     :
> 	libevent2-2.0.22_1
> 	ncurses-6.0_2
> 
> And the problem persists with the display errors.
> 
> If I use my workaround and install the following libmap entry, I get tmux to
> link to the ports ncurses, and then the display bugs go away.
> 
> [root at lorax]# cat /usr/local/etc/libmap.d/tmux.conf
> [tmux]
> libncurses.so.8	libncurses.so.6
> [root at lorax]# ldd /usr/local/bin/tmux
> /usr/local/bin/tmux:
> 	libutil.so.9 => /lib/libutil.so.9 (0x80088c000)
> 	libncurses.so.8 => /usr/local/lib/libncurses.so.6 (0x800a9e000)
> 	libevent-2.0.so.5 => /usr/local/lib/libevent-2.0.so.5 (0x800cc3000)
> 	libulog.so.0 => /lib/libulog.so.0 (0x800f06000)
> 	libc.so.7 => /lib/libc.so.7 (0x801108000)
> 	libtinfo.so.6 => /usr/local/lib/libtinfo.so.6 (0x8014b4000)
> 	libthr.so.3 => /lib/libthr.so.3 (0x8016eb000)
> 	libmd.so.6 => /lib/libmd.so.6 (0x80190f000)
> 
> 
> I tried modifying the port to set USES=ncurses:port and also added the
> NCURSES_RPATH=yes variable. Neither one resulted in a suitable library link.
> 
> While this is immediately noticed using tmux, I think it may be all ports
> that are affected. For example, the sysutils/tty-clock port also specifies
> USES=ncurses yet links to the base system ncurses when ports ncurses is
> installed.
> 
> 
> [root at lorax]# uname -r
> 10.2-RELEASE-p7

Hello,
While I'm not the Maintainer; it appears to me that the port is
choosing the $BASE version library, before attempting to use the
ports version. As seen here:

LIBEVENT_STATIC_BUILD_DEPENDS= ${LOCALBASE}/lib/libevent.a:devel/libevent2

Note that devel/libevent2 is chosen *after* ${LOCALBASE}

Have you attempted to reverse that order, and try again?

--Chris

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the freebsd-ports-bugs mailing list