New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
_curses, _curses_panel & _multiprocessing can't be build in 2.6b3 w/ SunStudio 12 #48036
Comments
I'm trying to compile Python 2.6b3 using Sun Studio 12 on a Solaris 10 [...] --($ ~/Source/Python-2.6b3)-- /opt/SUNWspro/bin/version The following components are installed on your system: Sun Studio 12 version of "/opt/SUNWspro/bin/../prod/bin/../../bin/cc": Sun C 5.9 --($ ~/Source/Python-2.6b3)-- CC -V --($ ~/Source/Python-2.6b3)-- cc -V --($ ~/Source/Python-2.6b3)-- gmake Failed to find the necessary bits to build these modules: Failed to build these modules: running build_scripts |
As for the multiprocessing problem, it has been fixed recently on trunk. |
Yes, the multiprocessing problem has been fixed by the patch in bpo-3110. |
Why do you think this is a bug in Python? It sounds like a bug in the (actually, it's two bugs - please use separate bug reports in the future: |
I filed that as a bug against Python 2.6, because in 2.5.2, the curses |
So would you like to work on a patch? |
Yes, I would _like_ to do that, but I fear that I lack the necessary |
Solaris has both traditional System V curses and an XPG4-compatible If you want the XPG4 compatible curses, you need to make sure The difficulty for Python is that it also tries to build a readline There are at least two ways around this:
There is, however, no XPG4 panels library, since panels was not part of |
For those not desiring the use of the chgat function and wishing |
EKIT.patch is not correct: it fails to find mvwchgat() on Linux, whereas the function is present. The test program is not linked to curses nor ncurses. << Solaris has both traditional System V curses and an XPG4-compatible ...
Link _curses module to a different curses library than the library used by readline may lead to crash: see issue bpo-7384. |
I hacked setup.py and _cursesmodule.c to use XPG4 curses. It requires many hacks because it lacks functions like getattrs() or getsyx/setsyx, constant like KEY_MIN and KEY_MAX. It looks difficult to use this curses library. |
I opened the issue bpo-13552 to list all curses issues on OpenIndiana. |
The attached patch allows _curses and _curses_panel to build with the sunpro compiler on Solaris11. The only changes were compiler/linker options in the main setup.py. The interactive curses_test works on my system. I can easily make patches for python2.7 and python3.2 as well. This patch may also address the issue in bug 13552 as well. |
+ # work around for assumption on line 128 of Modules/_cursesmodule.c Is it impossible to fix the offending code instead of working around it in setup.py? |
I am sure that macro object is there for good reason, it just doesn't apply
|
bpo-31919 have made _curses be built on OpenIndiana with the default curses library. I suppose this have fixed this issue on Solaris too. But configuring _curses to use XPG4 curses is a different issue. |
Solaris isn't a PEP-11 supported platform, I might suggest closing this issue. A |
There is @kulikjak who is interested in improving Solaris support in Python. If we close all Solaris issues, maybe it would be useful to add an |
A meta-ticket or project board could be better than a label! |
I would prefer to not create a project if the OS is not supported by PEP 11. The purpose of PEP 11 is to reduce the maintenance burden. Adding a project increases the maintenance burden: who maintains the project? what should people do with this project? |
Oh, I didn't know about this issue. I recently created #91964 to fix this/similar issue. As for listing all the issues, all of those I created have Solaris in their name so searching from them should be simple enough (at least those created by me). Closing this issue seems reasonable - it's filed against fairly old runtime, and we are not using Sun/Solaris Studio to compile Python for some time and AFAIK neither do other Solaris distributions. As for other PRs filed against Solaris, Is there something I can do to help with them being reviewed / merged? Would it e.g., help if those were reviewed by people from other Solarises (I believe I know somebody from both Illumos and OmniOS)? I am happy to help with whatever is necessary to get them merged. |
Closing per Jakub's rationale. I agree with Victor -- I'm not searching activley for Solaris issues to close them, but given the update to PEP 11 it would be useful to know what the rules of engagement are for unsupported platforms. Given anyone can create a project on their own fork and add issues, perhaps @kulikjak could create one on an offical Solaris / Oracle fork of CPython to track solaris related issues? A |
Well, I guess that's possible, but do you think that anybody except for me would realistically look there for Solaris related issues? How would that work? |
I am interested in Python working in Solaris/Illumos platforms too. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: