[python27 0005254]: _curses.so is missing python27 (2.7.8, REV=2014.09.23) (sparc solaris 10 9/10)
Mantis Bug Tracker via bug-notifications
bug-notifications at lists.opencsw.org
Mon Oct 19 16:22:58 CEST 2015
A NOTE has been added to this issue.
======================================================================
https://www.opencsw.org/mantis/view.php?id=5254
======================================================================
Reported By: jubal
Assigned To: dam
======================================================================
Project: python27
Issue ID: 5254
Category:
Reproducibility: always
Severity: block
Priority: normal
Status: assigned
======================================================================
Date Submitted: 2015-10-15 13:39 CEST
Last Modified: 2015-10-19 16:22 CEST
======================================================================
Summary: _curses.so is missing python27
(2.7.8,REV=2014.09.23) (sparc solaris 10 9/10)
Description:
Hi folks! It looks like there's a bug in the python27 build. Maybe it was
linked against /lib/libcurses.so instead of ncurses or something?
I would love to avoid building python from scratch on these machines - you
guys do such a great job :)
======================================================================
----------------------------------------------------------------------
(0011070) jubal (reporter) - 2015-10-19 16:22
https://www.opencsw.org/mantis/view.php?id=5254#c11070
----------------------------------------------------------------------
Apologies sir, I'm just barely getting my feet with wet with mgar :)
When I build the package with out libssl_dev installed, i get:
Python build finished, but the necessary bits to build these modules were
not found:
_bsddb _ssl _tkinter
bsddb185 linuxaudiodev ossaudiodev
To find the necessary bits, look in setup.py in detect_modules() for the
module's name.
But after installing libssl_dev (via pkgutil -i libssl_dev), the _ssl
module builds cleanly. I inferred that adding BUILD_DEP_PKGS +=
CSWlibssl-dev would force the dependency at build time -- is there a better
way?
(I'm just trying to orient myself with the right way to resolve)
Thanks sir!
More information about the bug-notifications
mailing list