Python 2.3.2 build on AIX 5.2L Power3

[Dr. Tom Cortese]

Hello,

I noticed the following message when trying to build Python 2.3.2
on AIX 5.2L on our Power3 machine:

configure: WARNING: term.h: present but cannot be compiled
configure: WARNING: term.h: check for missing prerequisite headers?
configure: WARNING: term.h: proceeding with the preprocessor's result
configure: WARNING:     ## ------------------------------------ ##
configure: WARNING:     ## Report this to address@hidden ##
configure: WARNING:     ## ------------------------------------ ##


I passed the following flags to "configure", and I do not have
root access:

./configure --prefix=/u/home/tcortese/mypython232 
--exec-prefix=/u/home/tcortese/mypython232 --disable-ipv6 
--without-threads

If I don't include the "--without-threads" flag, I see many
errors of the form "sem_[trywait|wait|post] -- permission denied"
during the "make" stage; these errors do not appear to bepresent when I
specify "--without-threads".

Also, near the beginning of the "make", I see the following error:

        cc_r -c  -DNDEBUG -O -I. -I./Include  -DPy_BUILD_CORE -o 
Parser/node.o Parser/node.c
        cc_r -c  -DNDEBUG -O -I. -I./Include  -DPy_BUILD_CORE -o 
Parser/parser.o Parser/parser.c
"Parser/parser.c", line 32.31: 1506-1298 (W) The subscript 500 is out of 
range. The valid range is 0 to 499.
"Parser/parser.c", line 265.45: 1506-1298 (W) The subscript 500 is out of 
range. The valid range is 0 to 499.
"Parser/parser.c", line 284.29: 1506-1298 (W) The subscript 500 is out of 
range. The valid range is 0 to 499.

Much further down in the "make", I noticed the following:

cc_r -DNDEBUG -O -I. -I/u/home/tcortese/Python-2.3.2/./Include 
-I/u/home/tcortese/Python-2.3.2/Include -I/u/home/tcortese/Python-2.3.2 -c 
/u/home/tcortese/Python-2.3.2/Modules/_cursesmodule.c -o 
build/temp.aix-5.2-2.3/_cursesmodule.o
./Modules/ld_so_aix cc_r -bI:Modules/python.exp 
build/temp.aix-5.2-2.3/_cursesmodule.o -lcurses -o 
build/lib.aix-5.2-2.3/_curses.so
building 'bz2' extension
cc_r -DNDEBUG -O -I. -I/u/home/tcortese/Python-2.3.2/./Include 
-I/u/home/tcortese/Python-2.3.2/Include -I/u/home/tcortese/Python-2.3.2 -c 
/u/home/tcortese/Python-2.3.2/Modules/bz2module.c -o 
build/temp.aix-5.2-2.3/bz2module.o
"/u/home/tcortese/Python-2.3.2/Modules/bz2module.c", line 12.10: 1506-296 
(S) #include file <bzlib.h> not found.
"/u/home/tcortese/Python-2.3.2/Modules/bz2module.c", line 103.9: 1506-046 
(S) Syntax error.
"/u/home/tcortese/Python-2.3.2/Modules/bz2module.c", line 114.9: 1506-046 
(S) Syntax error.
"/u/home/tcortese/Python-2.3.2/Modules/bz2module.c", line 123.9: 1506-046 
(S) Syntax error.
"/u/home/tcortese/Python-2.3.2/Modules/bz2module.c", line 139.22: 1506-045 
(S) Undeclared identifier BZ_OK.
"/u/home/tcortese/Python-2.3.2/Modules/bz2module.c", line 139.22: 1506-051 
(S) Case expression must be a valid integral constant.
"/u/home/tcortese/Python-2.3.2/Modules/bz2module.c", line 140.22: 1506-045 
(S) Undeclared identifier BZ_STREAM_END.
"/u/home/tcortese/Python-2.3.2/Modules/bz2module.c", line 140.22: 1506-051 
(S) Case expression must be a valid integral constant.
"/u/home/tcortese/Python-2.3.2/Modules/bz2module.c", line 152.22: 1506-045 
(S) Undeclared identifier BZ_PARAM_ERROR.
"/u/home/tcortese/Python-2.3.2/Modules/bz2module.c", line 152.22: 1506-051 
(S) Case expression must be a valid integral constant.
"/u/home/tcortese/Python-2.3.2/Modules/bz2module.c", line 159.22: 1506-045 
(S) Undeclared identifier BZ_MEM_ERROR.
"/u/home/tcortese/Python-2.3.2/Modules/bz2module.c", line 159.22: 1506-051 
(S) Case expression must be a valid integral constant.
"/u/home/tcortese/Python-2.3.2/Modules/bz2module.c", line 164.22: 1506-045 
(S) Undeclared identifier BZ_DATA_ERROR.
...
... many more like this
...

In spite of these errors (and I may have missed a few; I didn't
redirect output to a file, I just noticed these flying by as
"configure" and "make" were running), a  "python" executable is
created, but all of these build errors make me somewhat
nervous -- any ideas?

Thanks,

        -Tom Cortese
        PET Computational Environments Onsite