It seems you're on the right track, but still I have no clue why modpy.sh /usr/bin/python is using /usr/lib64/python2.3/lib-dynload/math.so if all env variables seem to be pointing to the modeller install only, or is that even the problem? (I added echoes to modpy.sh):
> ls $PYTHONHOME PYTHONHOME: Undefined variable.
> /usr/bin/python Python 2.3.4 (#1, Oct 13 2006, 15:53:00) [GCC 3.3.4 (pre 3.3.5 20040809)] on linux2 Type "help", "copyright", "credits" or "license" for more information.
>>> import math >>>
>modpy.sh /usr/bin/python LD_LIBRARY_PATH /gremlin/people/trippm/modeller9v5/lib/x86_64-intel8 DYLD_LIBRARY_PATH /gremlin/people/trippm/modeller9v5/lib/x86_64-intel8
PYTHONPATH /gremlin/people/trippm/modeller9v5/lib/x86_64-intel8:/gremlin/people/trippm/modeller9v5/modlib LIBPATH /gremlin/people/trippm/modeller9v5/lib/x86_64-intel8 ORIGPYPATH Python 2.3.4 (#1, Feb 15 2006, 18:08:24)
[GCC 3.4.4 20050721 (Red Hat 3.4.4-2)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import math Traceback (most recent call last):
File "<stdin>", line 1, in ? ImportError: /usr/lib64/python2.3/lib-dynload/math.so: undefined symbol: PyFPE_jbuf >>>
Mauricio Carrillo Tripp wrote:
> I'm getting a new error now though, and to me it looks like I have an
> incomplete installation of python2.3,
> but I could be wrong...
> File "/usr/lib64/python2.3/random.py", line 42, in ?
> from math import log as _log, exp as _exp, pi as _pi, e as _e
> ImportError: /usr/lib64/python2.3/lib-dynload/math.so: undefined symbol:
That's an odd one - my searches suggest that it's a version mismatch
somewhere - are you sure that math.so and your Python interpreter are
the same version? To be absolutely sure it's not some odd conflict with
Modeller, you could just run "python" by itself (no modpy.sh prefix) and
then type "import math" at the >>> prompt. "python" also reports its
version number when it starts. (Then try the same thing *with* the
modpy.sh prefix.) The error message shows you're using Python 2.3
modules - check to make sure the interpreter is also reporting it's 2.3.
If there's a mismatch, perhaps you still have the PYTHONHOME variable set.