[issue15050] Python 3.2.3 fail to make

Ezio Melotti added the comment: I'm going to close this as out of date. Feel free to reopen if it turns out that this is indeed a Python issue. -- nosy: +ezio.melotti resolution: -> out of date stage: -> committed/rejected status: open -> closed _

[issue15050] Python 3.2.3 fail to make

Martin v. Löwis added the comment: > Martin, do I understand that you are saying that this is not a Python > problem, and should be closed? No. I'm saying that I don't know whether it's a Python problem. It hasn't been fully analyzed. I actually only suspect that it's a misconfiguration. -

[issue15050] Python 3.2.3 fail to make

Terry J. Reedy added the comment: Martin, do I understand that you are saying that this is not a Python problem, and should be closed? -- nosy: +terry.reedy ___ Python tracker

[issue15050] Python 3.2.3 fail to make

Martin v. Löwis added the comment: This is a misconfiguration of your system. Take a look at line 29538 of config.log. It says configure:13701: ./conftest ld.so.1: ./conftest: ÖÂÃüµÄ: libintl.so.8: ´ò¿ªÊ§°Ü: ÎÞ´ËÎļþ»òĿ¼ ./configure: line -1756: 8400 Killed ./conftest$ac_ex

[issue15050] Python 3.2.3 fail to make

Grey_Shao added the comment: Thanks for your kindly help I attach the config.log in the attachment "data.7z" The value of the PRId64 is: #ifdef _LP64 #define PRId64 "ld" #else /* _ILP32 */ #if __STDC__ - 0 == 0 && !defined(_NO_LONGLONG) #define PRId64

[issue15050] Python 3.2.3 fail to make

Martin v. Löwis added the comment: Can you please attach the config.log file also? Also, can you please report what the value of PRId64 in /usr/include/inttypes.h is? -- nosy: +loewis ___ Python tracker

[issue15050] Python 3.2.3 fail to make

New submission from Grey_Shao : When I try to compile the Python 3.2.3, I failed to make After I ungzip and untar the source package of the Python 3.2.3, Then run the following commands: 1. ./configure 2. make When step 2, the errors below happens: gcc -c -fno-strict-aliasing -DNDEBUG -g