Date: Fri, 15 Jan 2016 07:20:22 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: maintainer-feedback requested: [Bug 206285] lang/python35: _curses.so not linked against libncursesw even when available Message-ID: <bug-206285-21822-4LpE3X934w@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-206285-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-206285-21822@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
Brendan Molloy <brendan+freebsd@bbqsrc.net> has reassigned Bugzilla Automation <bugzilla@FreeBSD.org>'s request for maintainer-feedback to FreeBSD Python <python@FreeBSD.org>: Bug 206285: lang/python35: _curses.so not linked against libncursesw even when available https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206285 --- Description --- When installing via pkg, Python 3.5's `curses` module (_curses.so) links against /lib/ncurses.so.8 and not /lib/ncursesw.so.8 even though it is present, causing the `curses` module to fail with methods such as `window.get_wch()`. Same occurs when building from ports regardless of selected options. This issue is also present on Python 3.4 and 2.7 ports. Initial investigation seems to imply the setup.py file is not detecting correctly which library to link to. --- $ ldd /usr/local/lib/python3.5/lib-dynload/_curses.so /usr/local/lib/python3.5/lib-dynload/_curses.so: libthr.so.3 => /lib/libthr.so.3 (0x801614000) libncurses.so.8 => /lib/libncurses.so.8 (0x801838000) libpython3.5m.so.1.0 => /usr/local/lib/libpython3.5m.so.1.0 (0x801c00000) libc.so.7 => /lib/libc.so.7 (0x800821000) libintl.so.8 => /usr/local/lib/libintl.so.8 (0x80209b000) libutil.so.9 => /lib/libutil.so.9 (0x8022a6000) libm.so.5 => /lib/libm.so.5 (0x8024b8000)help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206285-21822-4LpE3X934w>