Date: Fri, 01 Jul 2016 06:04:42 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 206471] sysutils/tmux USES=ncurses seems to be a no-op Message-ID: <bug-206471-13-U0lXdnaumX@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-206471-13@https.bugs.freebsd.org/bugzilla/> References: <bug-206471-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206471 Chris Hutchinson <portmaster@bsdforge.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |portmaster@bsdforge.com --- Comment #1 from Chris Hutchinson <portmaster@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 >=20 > The TL;DR is that I needed tmux to be linked using the ports ncurses rath= er > than the system ncurses to avoid display errors in certain circumstances. >=20 > 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 n= ot > link to the ports ncurses. Perhaps it is that I'm running FreeBSD 10.2 no= w? >=20 > This is what I see: >=20 > [root@lorax]# ldd /usr/local/bin/tmux > /usr/local/bin/tmux: > libutil.so.9 =3D> /lib/libutil.so.9 (0x80088c000) > libncurses.so.8 =3D> /lib/libncurses.so.8 (0x800a9e000) > libevent-2.0.so.5 =3D> /usr/local/lib/libevent-2.0.so.5 (0x800ceb000) > libulog.so.0 =3D> /lib/libulog.so.0 (0x800f2e000) > libc.so.7 =3D> /lib/libc.so.7 (0x801130000) > libthr.so.3 =3D> /lib/libthr.so.3 (0x8014dc000) > libmd.so.6 =3D> /lib/libmd.so.6 (0x801700000) > [root@lorax]# pkg info -dr tmux > tmux-2.1_1 > Depends on : > libevent2-2.0.22_1 > ncurses-6.0_2 >=20 > And the problem persists with the display errors. >=20 > 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. >=20 > [root@lorax]# cat /usr/local/etc/libmap.d/tmux.conf > [tmux] > libncurses.so.8 libncurses.so.6 > [root@lorax]# ldd /usr/local/bin/tmux > /usr/local/bin/tmux: > libutil.so.9 =3D> /lib/libutil.so.9 (0x80088c000) > libncurses.so.8 =3D> /usr/local/lib/libncurses.so.6 (0x800a9e000) > libevent-2.0.so.5 =3D> /usr/local/lib/libevent-2.0.so.5 (0x800cc3000) > libulog.so.0 =3D> /lib/libulog.so.0 (0x800f06000) > libc.so.7 =3D> /lib/libc.so.7 (0x801108000) > libtinfo.so.6 =3D> /usr/local/lib/libtinfo.so.6 (0x8014b4000) > libthr.so.3 =3D> /lib/libthr.so.3 (0x8016eb000) > libmd.so.6 =3D> /lib/libmd.so.6 (0x80190f000) >=20 >=20 > I tried modifying the port to set USES=3Dncurses:port and also added the > NCURSES_RPATH=3Dyes variable. Neither one resulted in a suitable library = link. >=20 > 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=3Dncurses yet links to the base system ncurses when ports ncurses is > installed. >=20 >=20 > [root@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=3D ${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 --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206471-13-U0lXdnaumX>