[issue21392] Python on Cygwin: subprocess.call BlockingIOError: [Errno 11] Resource temporarily unavailable

2014-05-05 Thread dellair jie
dellair jie added the comment: Eric, Very much appreciated for your offer to help. This issue is with Cygwin fork(), documented here: http://cygwin.com/faq.html#faq.using.fixing-fork-failures I am closing the issue. Have a great day! -- resolution: - not a bug status: open - closed

[issue21124] _struct module compilation error under Cygwin 1.7.17 on Python 3.4

2014-04-30 Thread dellair jie
dellair jie added the comment: Fixed with the patch. -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21124

[issue21392] Python on Cygwin: subprocess.call BlockingIOError: [Errno 11] Resource temporarily unavailable

2014-04-30 Thread dellair jie
New submission from dellair jie: Folks, I am running Python 3.4 on Cygwin 1.7.17 on Windows 2008. The constant error I get is: Traceback (most recent call last): File M:/sb3_ljie/bce/cmTools/lib/CC.py, line 321, in standAlone results = Process.execute (cmd = cmd, opts = opts) File M

[issue21392] Python on Cygwin: subprocess.call BlockingIOError: [Errno 11] Resource temporarily unavailable

2014-04-30 Thread dellair jie
Changes by dellair jie dell...@gmail.com: -- components: +IO type: - resource usage ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21392

[issue21392] Python on Cygwin: subprocess.call BlockingIOError: [Errno 11] Resource temporarily unavailable

2014-04-30 Thread dellair jie
dellair jie added the comment: The value of __signal and __signalList: __signal=0 __signalList=[None] * 256 __signalList[signal.SIGHUP] = signalHandler __signalList[signal.SIGQUIT] = signalHandler __signalList[signal.SIGUSR1] = signalHandler __signalList[signal.SIGUSR2

[issue21124] _struct module compilation error under Cygwin 1.7.17 on Python 3.4

2014-04-29 Thread dellair jie
dellair jie added the comment: Hello masamoto, The patch you provided works quite well. The build passed and Python calls are successfully. Please let me know what else you need me to test in order to have the patch accepted or else feel free to close it with Resolution Fixed. Thanks, Dellair

[issue21085] compile error Python3.3 on Cygwin

2014-04-29 Thread dellair jie
dellair jie added the comment: Finally got it compiled on Cygwin! :) Victor, I am still having issue with the make test on Cygwin, hence can only do some manual testing: Output: info = signal.sigwaitinfo({signal.SIGINT}) ^C info = signal.struct_siginfo((2, 128, 0, 0, 0, 3)) Traceback

[issue21124] _struct module compilation error under Cygwin 1.7.17 on Python 3.4

2014-04-02 Thread dellair jie
dellair jie added the comment: Neil, It doesn't look like a duplicate of Issue6672. The one in Issue6672 was for Mingw, all the patches simply added __MINGW32__ to __CYGWIN__ build structure. While my issue is, the build failed with _struct.c on Cygwin. So the module is recognized, just

[issue21124] _struct module compilation error under Cygwin 1.7.17 on Python 3.4

2014-04-02 Thread dellair jie
dellair jie added the comment: Yamamoto, Thanks, the patch you offered did make the _struct error disappeared. I will do a bit more testing. Dellair -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21124

[issue21085] compile error Python3.3 on Cygwin

2014-04-01 Thread dellair jie
dellair jie added the comment: Martin, Here is the values presented on Python 3.4.0, in fact they are the same as 3.3.2, please note the key difference. /* #undef HAVE_SIGTIMEDWAIT */ #define HAVE_SIGWAIT 1 #define HAVE_SIGWAITINFO 1 The SIGTIMEDWAIT is undef while the SIGWAIT is defined

[issue21085] compile error Python3.3 on Cygwin

2014-04-01 Thread dellair jie
dellair jie added the comment: Victor, Would you please be more specific on test_signal? Br, Dellair -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21085

[issue21085] compile error Python3.3 on Cygwin

2014-04-01 Thread dellair jie
dellair jie added the comment: Victor, I suppose that Python needs to be built successfully before running test_signal. Three patches were applied in Python 3.4.0. However, the build failed to build _struct module. Should I open another Issue to track it? As long as the build goes through

[issue21123] Compilation error on _struct module on Python 3.4

2014-04-01 Thread dellair jie
New submission from dellair jie: Dear all, I am compiling Python 3.4 on Cygwin 1.7.17. The following has been done in order to reach the point where _struct module failed. A clean Python 3.4 Applied patches: cygwin_si_band.patch in Issue21085 0001-CYGWIN-issue13756-Python-make-fail

[issue21124] Compilation error on _struct module on Python 3.4

2014-04-01 Thread dellair jie
New submission from dellair jie: Dear all, I am compiling Python 3.4 on Cygwin 1.7.17. The following has been done in order to reach the point where _struct module failed. A clean Python 3.4 Applied patches: cygwin_si_band.patch in Issue21085 0001-CYGWIN-issue13756-Python-make-fail

[issue21124] Compilation error on _struct module on Python 3.4

2014-04-01 Thread dellair jie
dellair jie added the comment: The full build log -- Added file: http://bugs.python.org/file34696/Build.log ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21124

[issue21123] Compilation error on _struct module on Python 3.4

2014-04-01 Thread dellair jie
dellair jie added the comment: Duplicated with Issue21124 -- resolution: - duplicate status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21123

[issue21085] compile error Python3.3 on Cygwin

2014-03-31 Thread dellair jie
dellair jie added the comment: Yes, my pleasure. After configure on Cygwin, there is pyconfig.h generated, variables are as following: /* #undef HAVE_SIGTIMEDWAIT */ /* #define HAVE_SIGWAITINFO 1 */ The error disappeared once changed HAVE_SIGWAITINFO to undef. However, it encountered another

[issue21085] compile error Python3.3 on Cygwin

2014-03-31 Thread dellair jie
dellair jie added the comment: Applied the patch 0001-CYGWIN-issue13756-Python-make-fail-on-cygwin.patch in case: http://bugs.python.org/issue13756 The build failed with parser module: building 'parser' extension gcc -Wno-unused-result -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I

[issue21085] compile error Python3.3 on Cygwin

2014-03-31 Thread dellair jie
dellair jie added the comment: Martin, Certainly running on 3.4 now. The output of the command is attached. Will try to look into it tomorrow if no immediate follow up post. Br, Li -- Added file: http://bugs.python.org/file34682/signalmodule.output.txt

[issue21085] compile error Python3.3 on Cygwin

2014-03-31 Thread dellair jie
dellair jie added the comment: Martin, Thanks for the analysis! The following values came from Python 3.3.2, the #define HAVE_SIGWAITINFO 1 was without comment sign, I commented it out for the build to go through. /* #undef HAVE_SIGTIMEDWAIT */ /* #define HAVE_SIGWAITINFO 1 */ The output

[issue21085] compile error Python3.3 on Cygwin

2014-03-28 Thread dellair jie
New submission from dellair jie: Folks, Is Cygwin supported by Python? We met the following error when compiling Python 3.3.2 on Cygwin 1.7.17: gcc -c -Wno-unused-result -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I. -IInclude -I./Include-DPy_BUILD_CORE -o Modules/main.o

[issue20163] ValueError: time data does not match format

2014-03-28 Thread dellair jie
dellair jie added the comment: We've found a workaround to handle the timestr manually. Thanks, -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20163

[issue21085] compile error Python3.3 on Cygwin

2014-03-28 Thread dellair jie
dellair jie added the comment: Victor, I did do ./configure, without any parameters. Should I use it with --without-signal-module option? Will all signals be disabled if this option is specified? From Python document, it mentions Windows support the following signals: signal.SIGINT

[issue20163] ValueError: time data does not match format

2014-01-07 Thread dellair jie
New submission from dellair jie: Hello, We are using Python 3.3.2 for HPUX11.31. The following error happens only on HPUX, works on SunOS, RHEL, AIX. python Python 3.3.2 (default, Dec 9 2013, 14:04:25) [C] on hp-ux11 Type help, copyright, credits or license for more information. from

[issue20163] ValueError: time data does not match format

2014-01-07 Thread dellair jie
dellair jie added the comment: Victor, Thanks for the comment. Isolated, the error happens at: import time time.strptime (Dec, %b) Traceback (most recent call last): File stdin, line 1, in module File /python/lib/python3.3/_strptime.py, line 494, in _strptime_time tt = _strptime

[issue20163] ValueError: time data does not match format

2014-01-07 Thread dellair jie
dellair jie added the comment: The output of command: $ date +'%b' Jan $ uname -a HP-UX test5 B.11.31 U ia64 4201936010 unlimited-user license -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20163

[issue20163] ValueError: time data does not match format

2014-01-07 Thread dellair jie
dellair jie added the comment: We get an empty string for the name. :) time.strftime(%b, time.gmtime(1387036705)) '' -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20163

[issue20163] ValueError: time data does not match format

2014-01-07 Thread dellair jie
dellair jie added the comment: Victor, HPUX 11.31 was first released in 2007, we keep upgrading and the latest update is in 2013. ^_^ A workaround sounds fine. By re-implementing strftime(), do you mean to patch it from: http://bugs.python.org/issue1777412

[issue19661] AIX: Python: RuntimeError invalid slot offset when importing a module in _ssl module

2013-12-10 Thread dellair jie
dellair jie added the comment: Folks, I am closing this bug as it seems to be fixed with a with a redownload of original package. Thanks for sharing the ideas. Br, Li -- resolution: - fixed status: open - closed ___ Python tracker rep

[issue19661] AIX: Python: RuntimeError invalid slot offset when importing a module in _ssl module

2013-11-27 Thread dellair jie
dellair jie added the comment: I have rebuilt Python 3.3.2 with GCC 4.4.0 on AIX6.1. There was no warning. But, still seeing the same import offset runtime error: gcc -pthread -DNDEBUG -g -fwrapv -O0 -Wall -Wstrict-prototypes -IInclude -I. -Iopenssl/include -Iopenssl/include -IPython/Python

[issue19661] AIX: Python: RuntimeError invalid slot offset when importing a module in _ssl module

2013-11-24 Thread dellair jie
dellair jie added the comment: It would be appreciated if someone could shed some lights on how to rebuild a single module (ssl) from source code package and import it to python. Thanks in advance! -- ___ Python tracker rep...@bugs.python.org http

[issue19661] AIX: Python: RuntimeError invalid slot offset when importing a module in _ssl module

2013-11-22 Thread dellair jie
dellair jie added the comment: Folks, Is there a patch to apply on this, I tried to search online, found one similar post but was solved until the poster switched to another version of xlc. Do we need to use another compiler(I will have to build though)? Please don't hesitate to contact me

[issue19661] AIX: Python: RuntimeError invalid slot offset when importing a module in _ssl module

2013-11-21 Thread dellair jie
dellair jie added the comment: Still seeing the same error without optimization, the build log from HPUX 11.31IA is also attached for reference (maybe irrelevance though ^^): AIX 6.1: cc -qlanglvl=extc89 -O0 -IInclude -I. -I/usr/local/include -c /aix/Modules/_ssl.c -o build/temp.aix-6.1-3.3

[issue19661] Python: RuntimeError: invalid slot offset when importing a module

2013-11-20 Thread dellair jie
New submission from dellair jie: Dear all, I am getting above error when trying to import ssl module. In fact, the error showed up during the build and _ssl module was added to the failed module list. However, the compilation and link went well. There was no error on compilation and link