Yes, the problem is with 32-vs-64. At first, I have found an ugly workaround of getting 32-bit version of libguile-srfi-srfi-1-v-3.so.3 and changing the symbolic link in /usr/lib to fool coot into using it. Coot will start but will be quite unstable. So to answer your question, there is no decent way of fixing this without compiling coot.
What worked for me (eventually) was to build coot using autobuilder scripts. This is not without caveat, since guile-1.8.5 fails to compile on Jaunty. I don't know if the autobuilder script was updated to fix this, but here is what I had to do to get it to work: https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0905&L=COOT&T=0&O=A&P=48558 Seriously, with autobuilder scripts it will take very little time, probably less than it took me to write this message. On Fri, 2009-07-03 at 17:18 -0400, Thomas J Magliery PhD wrote: > Hi, I just installed the 64-bit version of Ubuntu 9.04 Desktop, and then > I installed CCP4 6.1.1 using the standard package and installation > script. I can run ccp4i successfully. However, when I try to run Coot, > I get a bunch of errors. I think the problem is that Coot was compiled > with 32-bit libraries, which I don't have. > > Is there some way to fix this without compiling Coot or re-installing > with 32-bit Ubuntu? Who knows how, but I have CCP4 (6.0.2) and Coot > (0.5-pre-1) working on my 64-bit FC8 laptop. > > Thanks, > Tom > > === > COOT_PREFIX is /usr/local/CCP4/Coot-0.5.2 > /usr/local/CCP4/Coot-0.5.2/bin/coot-real > Acquiring application resources from > /usr/local/CCP4/Coot-0.5.2/share/coot/cootrc > Gtk-Message: Failed to load module "canberra-gtk-module": > /usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so: wrong ELF class: > ELFCLASS64 > INFO:: splash_screen_pixmap_dir > /usr/local/CCP4/Coot-0.5.2/share/coot/pixmaps > INFO:: Colours file: /usr/local/CCP4/Coot-0.5.2/share/coot/colours.def > loaded > INFO:: Using Standard CCP4 Refmac dictionary from CLIBD_MON: > /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers/ > There are 118 data in > /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//list/mon_lib_list.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//a/ALA.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//a/ASP.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//a/ASN.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//c/CYS.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//g/GLN.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//g/GLY.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//g/GLU.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//p/PHE.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//h/HIS.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//i/ILE.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//l/LYS.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//l/LEU.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//m/MET.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//m/MSE.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//p/PRO.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//a/ARG.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//s/SER.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//t/THR.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//v/VAL.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//t/TRP.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//t/TYR.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//p/PO4.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//s/SO4.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//g/GOL.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//e/ETH.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//c/CIT.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//a/AR.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//a/AD.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//c/CR.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//c/CD.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//g/GR.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//g/GD.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//t/TD.cif > There are 2 data in /usr/local/CCP4/ccp4-6.1.1/lib/data/monomers//u/UR.cif > Reading coordinate file: > /usr/local/CCP4/Coot-0.5.2/share/coot/standard-residues.pdb > PDB file /usr/local/CCP4/Coot-0.5.2/share/coot/standard-residues.pdb has > been read. > Spacegroup: P 1 > Cell: 40.631 109.18 93.243 90 90 90 > /usr/lib/gio/modules/libgioremote-volume-monitor.so: wrong ELF class: > ELFCLASS64 > Failed to load module: /usr/lib/gio/modules/libgioremote-volume-monitor.so > /usr/lib/gio/modules/libgvfsdbus.so: wrong ELF class: ELFCLASS64 > Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so > /usr/lib/gio/modules/libgiogconf.so: wrong ELF class: ELFCLASS64 > Failed to load module: /usr/lib/gio/modules/libgiogconf.so > initalize graphics molecules...done. > (filter-fileselection-filenames-state) > (get-active-map-drag-flag) > (use-graphics-interface-state) > ERROR: In procedure dynamic-link: > ERROR: file: "libguile-srfi-srfi-1-v-3", message: > "/usr/lib/libguile-srfi-srfi-1-v-3.so.3: wrong ELF class: ELFCLASS64" > Gtk-Message: Failed to load module "canberra-gtk-module": > /usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so: wrong ELF class: > ELFCLASS64 > coot-exe: "/usr/local/CCP4/Coot-0.5.2/bin/coot-real" > coot-version: > /usr/local/CCP4/Coot-0.5.2/bin/coot-real > core: #f > No core file found. No debugging > === > > P.S. Hi Paul. > --
