Date: Fri, 15 Jan 2016 07:20:22 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 206285] lang/python35: _curses.so not linked against libncursesw even when available Message-ID: <bug-206285-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206285 Bug ID: 206285 Summary: lang/python35: _curses.so not linked against libncursesw even when available Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: python@FreeBSD.org Reporter: brendan+freebsd@bbqsrc.net Flags: maintainer-feedback?(python@FreeBSD.org) Assignee: python@FreeBSD.org 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 pres= ent, 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 =3D> /lib/libthr.so.3 (0x801614000) libncurses.so.8 =3D> /lib/libncurses.so.8 (0x801838000) libpython3.5m.so.1.0 =3D> /usr/local/lib/libpython3.5m.so.1.0 (0x801c00000) libc.so.7 =3D> /lib/libc.so.7 (0x800821000) libintl.so.8 =3D> /usr/local/lib/libintl.so.8 (0x80209b000) libutil.so.9 =3D> /lib/libutil.so.9 (0x8022a6000) libm.so.5 =3D> /lib/libm.so.5 (0x8024b8000) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206285-13>