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 -fwrapv -O3 -Wall -Wstrict-prototypes    -I. -IInclude -I./Include    -DPy_BUILD_CORE -o Mod
ules/python.o ./Modules/python.c
In file included from Include/Python.h:50,
                 from ./Modules/python.c:3:
Include/pyport.h:260:13: #error "This platform's pyconfig.h needs to define PY_FORMAT_LONG_LONG"
*** Error code 1
make: Fatal error: Command failed for target `Modules/python.o'

Can you help me

My system OS is:
uname -a
SunOS HPCT01 5.9 Generic_117171-02 sun4u sparc SUNW,Sun-Fire-280R

I attached install history file

Thanks

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?

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                  "lld"
    #endif
    #endif
I also attach the related inttypes.h files in the attachment "data.7z"

Thanks for your help

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_exeext
configure:13701: $? = 137
configure: program exited with status 137
configure: failed program was:
| /* confdefs.h */
| #define _GNU_SOURCE 1
...

So it didn't actually run the test, but immediately failed because libintl.so.8 is broken (or something involving libintl.so.8).

The surprising part is that this starts with the test for PTHREAD_SCOPE_SYSTEM. 

I cannot provide an explanation for that - you will have to research the source of the problem yourself.

Martin, do I understand that you are saying that this is not a Python problem, and should be closed?

> 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.

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.