|
[Rivet] rivet and problems with python libAndy Buckley andy.buckley at ed.ac.ukMon Feb 14 16:11:38 GMT 2011
Zenonas Zenonos wrote: > Hello Andy > > thanks for looking at this. > Previously, I was running with python 2.5.4p2, Rivet > 1.2.1, slc4_amd64_gcc34, AGILe-1.1.4 and it was working fine. > Now, I moved to py 2.6.2, rivet > 1.4.0, x86_64-slc5-gcc43-opt, AGILe-1.2.1 and I'm having this python > problem. > > The result of doing "locate libpython2.6.so.1.0" interactively is good > /usr/lib64/libpython2.6.so.1.0 > but empty when running with bsub. Which path must be normally taken when > running? > In the other hand, I saw that libpython2.4.so.1.0 exist when running > with bsub. What might be the solution to that? Ok, your workstation has Python 2.6 installed as part of the OS, so your builds of Rivet & AGILe have used that and will require that there is a corresponding library in the library lookup path when running. From your bsub check, the batch system is not the same OS, and does not have a system copy of Python 2.6.2. So unless you find a 64 bit libpython2.6.so.1.0 on the batch system, it's not going to run successfully. > How can I point to libpython2.6.so.1.0 correctly when running with bsub? You'll have to find one first! There might be a suitable library on AFS in the Python installations under /afs/cern.ch/sw/lcg/... if you can find one, then in your batch script add a line to add its containing directory to the runtime loader path, e.g. "export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/afs/cern.ch/sw/lcg/python/2.6.2/x86_64-slc5-gcc43-opt/lib" (I just made that path up... you should check for yourself!) Hope that helps, Andy -- Dr Andy Buckley SUPA Advanced Research Fellow Particle Physics Experiment Group, University of Edinburgh The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.
More information about the Rivet mailing list |