On Jan 27, 2010, at 11:23 AM, Erick Antezana wrote:
Unfortunately, we have in our system GLIBC 2.5 (glibc-2.5-42.el5_4.2).
We have tried to bypass such requirement by compiling pysam and
manually copying the csamtools.so file without success. Once I try to
launch Galaxy (run.sh) it fetches the original egg (and so library)...
The variable FETCH_EGGS was set to 0 but it is still fetching the
latest versions...Are we missing something? Otherwise, would it be
possible to have such egg for glib 2.5 ?
You may build your pysam version with
python setup.py bdist_egg
and then copy it to $GALAXYPATH/eggs/py-VERSION-OS-egg/pysam-VERSION-OSRELEASE.egg
so next time you run galaxy it will find your egg in the right place with the right name :-)