Thanks for your help. Actually that's another question I had you just answered!. I have removed all env variables. 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...
#!/bin/bash -v
export -p LD_LIBRARY_PATH= export -p PATH=${PATH}:/usr/people/trippm/bin/modeller9v5/bin ## limit stacksize unlimited
echo "Running model-fast.py" Running model-fast.py modpy.sh python model-fast.py > model-fast.log
echo "Running model-parallel.py" Running model-parallel.py modpy.sh python model-parallel.py > model-parallel.log Traceback (most recent call last): File "model-parallel.py", line 4, in ? from modeller.parallel import * File "/usr/people/trippm/bin/modeller9v5/modlib/modeller/parallel/__init__.py", line 1, in ? from job import job File "/usr/people/trippm/bin/modeller9v5/modlib/modeller/parallel/job.py", line 1, in ? import socket, random, os, select 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: PyFPE_jbuf
On Fri, Dec 5, 2008 at 12:56 PM, Modeller Caretaker < modeller-care@salilab.org> wrote:
> Mauricio Carrillo Tripp wrote: > > You where right, I unset the LD_LIBRARY_PATH variable and the error went > > away. > > libsvml.so is indeed in the same location as libmodeller.so.4 > > However, it took me back to the initial problem: > > > > export -p LD_LIBRARY_PATH= > > export -p PYTHONHOME=/usr/lib64/python2.3/ > > export MODINSTALL9v5=/****/modeller9v5 > > export EXECUTABLE_TYPE9v5=x86_64-intel8 > > export -p LIBS_LIB9v5=${MODINSTALL9v5}/modlib/libs.lib > > export KEY_MODELLER9v5=**** > > export -p PATH=${PATH}:${MODINSTALL9v5}/bin > > ## limit stacksize unlimited > > This problem is most likely caused by your setting PYTHONHOME. You don't > actually need to set *any* of the environment variables you have above > (except PATH, I guess, unless you want to put in the full path to > modpy.sh) - clear them all and the problem should go away. > > BTW, there is also no need to set any of these variables to run the > mod9v5 script - it sets them itself anyway. Maybe you are reading a very > old version of the Modeller documentation? We certainly don't recommend > setting any environment variables these days. > > Ben Webb, Modeller Caretaker > -- > modeller-care@salilab.org http://www.salilab.org/modeller/ > Modeller mail list: http://salilab.org/mailman/listinfo/modeller_usage >