Cray T3E: Mark Hadfield (m.hadfield@niwa.co.nz) writes:

Python can be built satisfactorily on a Cray T3E but based on

my experience with the NIWA T3E (2002-05-22, version 2.2.1)

there are a few bugs and gotchas. For more information see a

thread on comp.lang.python in May 2002 entitled "Building

Python on Cray T3E".

1) Use Cray's cc and not gcc. The latter was reported not to

work by Konrad Hinsen. It may work now, but it may not.

2) To set sys.platform to something sensible, pass the

following environment variable to the configure script:

MACHDEP=unicosmk

2) Run configure with option "--enable-unicode=ucs4".

3) The Cray T3E does not support dynamic linking, so extension

modules have to be built by adding (or uncommenting) lines

in Modules/Setup. The minimum set of modules is

posix, new, _sre, unicodedata

On NIWA's vanilla T3E system the following have also been

included successfully:

_codecs, _locale, _socket, _symtable, _testcapi, _weakref

array, binascii, cmath, cPickle, crypt, cStringIO, dbm

errno, fcntl, grp, math, md5, operator, parser, pcre, pwd

regex, rotor, select, struct, strop, syslog, termios

time, timing, xreadlines

4) Once the python executable and library have been built, make

will execute setup.py, which will attempt to build remaining

extensions and link them dynamically. Each of these attempts

will fail but should not halt the make process. This is

normal.

5) Running "make test" uses a lot of resources and causes

problems on our system. You might want to try running tests

singly or in small groups.