Hi Igor,
regarding my recent ranting against Watcom C … the roots of my problems with
the port of the newest Python version was not the compiler and it was not the
libc. The first steps using ‘configure’ went wrong. The sequence
configure … make distclear … CC=cc configure created surprisingly a mixt
useage of gcc and Watcom headers =:-/ (which produced the strange stack
problems).
After reinstalling the Python sources … all is OK. No compiler problems,
no library problems … Python-1.6b1 now provides also Unicode for QNX4 
Regards
Armin