Python on Crays

[Carrie Farberow]

Ok, here are links to word documents outlining the commands I executed as well as the make.log file and the make_install.log file

instructions/commands:
https://mywebspace.wisc.edu/xythoswfs/webui/_xy-29018965_1-t_dSnfEm5b

make.log:
https://mywebspace.wisc.edu/xythoswfs/webui/_xy-29018966_1-t_zjqLuV5v
javascript:parent.send('smtp')
make_install.log:
https://mywebspace.wisc.edu/xythoswfs/webui/_xy-29018967_1-t_n8aqH2P

The issue referred to in the previous message (http://bugs.python.org/issue1594809) sounds similar - however I do not think that I can just build the shared unicodedata module and have it work properly, as I am trying to statically link the necessary modules.  I am very new with this, so if I am completely misunderstanding, please feel free to let me know.

Thanks!
Carrie

----- Original Message -----
From: Mark Dickinson <dickinsm at gmail.com>
Date: Friday, August 21, 2009 12:50 pm
Subject: Re: Python on Crays
To: python-list at python.org

> On Aug 21, 12:21 am, Carrie Farberow <farbe... at wisc.edu> wrote:
> > I am trying to build a statically-linked Python based on directions 
> at:
> >
> > http://yt.enzotools.org/wiki/CrayXT5Installation
> >
> > I have tried this on multiple systems.  The first time I attempt to 
> build python, 'make' runs fine but 'make install' fails with the 
> following error:
> >
> > Sorry: UnicodeError: ("\\N escapes not supported (can't load 
> unicodedata module)",)
> >
> > Any help regarding the source of this error and possible fixes would 
> be appreciated.
> 
> Hmm.  There's not a lot of information to go on here.
> What version of Python is this? Python 2.6.2?
> Have you tried Googling for that exact error message?
> 
> The following issue looks as though it might be relevant:
> 
> http://bugs.python.org/issue1594809
> 
> especially since it looks as though the directions you linked
> to involve messing with the PYTHONPATH environment variable.
> 
> If you could post a log somewhere[*] showing the exact commands
> that you executed, along with all the output (and especially
> all the output from 'make' and 'make install'), that might help
> someone diagnose the problem further.
> 
> Mark
> 
> [*] I'm not sure where, though.  Posting all that output directly
> in a newsgroup message might not be considered very friendly.
> -- 
> http://mail.python.org/mailman/listinfo/python-list