maintainer-feedback requested: [Bug 206285] lang/python35: _curses.so not linked against libncursesw even when available
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Fri Jan 15 07:20:22 UTC 2016
Brendan Molloy <brendan+freebsd at bbqsrc.net> has reassigned Bugzilla Automation
<bugzilla at FreeBSD.org>'s request for maintainer-feedback to FreeBSD Python
<python at 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)
More information about the freebsd-python
mailing list