Hi Fellows, following Kay's idea, I unpacked coot-0.6.2-binary-Linux-x86_64-centos-5-python-gtk2.tar.gz:
./bin/coot-real: error while loading shared libraries: libssl.so.6: cannot open shared object file: No such file or directory ok, I yum it to be safe, find it in /usr/lib/libssl.so.6 and export LD_LIBRARY_PATH=/usr/lib Now the vengeance of the ELF (soon coming to a workstation near you) is unleashed upon me: ./bin/coot-real: error while loading shared libraries: libssl.so.6: wrong ELF class: ELFCLASS32 coot-exe: "./bin/coot-real" Maybe I need the CLASS of 64 for my elf reunion? I guess I better let the pro's deal with this and wait for a new binary. Anyhow, thanks for all the tips. Cheers, BR PS: current rhel build version coot-0.6.2-binary-Linux-x86_64-rhel-4-gtk2.tar.gz ./bin/coot-real: error while loading shared libraries: libldap-2.2.so.7: cannot open shared object file: No such file or directory Yum: No package libldap-2.2.so.7 available. PPS: latest (32 bit?) prebuild coot-0.7-pre-1-revision-3999-binary-Linux-i386-rhel-5-python-gtk2.tar.gz After a lot of yumming Coot actually starts, but I get a lengthy error log and a version of the previously reported problem with the icon SVGs (sidebar mostly empty) PPPS: coot-0.7-pre-1-revision-3999-binary-Linux-x86_64-rhel-4-python-gtk2.tar.gz same as above with coot-0.6.2-binary-Linux-x86_64-rhel-4-gtk2.tar.gz PPPPS: definition of insanity: doing the same thing over and over and expecting a different outcome. -----Original Message----- From: Mailing list for users of COOT Crystallographic Software [mailto:[email protected]] On Behalf Of Kay Diederichs Sent: Thursday, February 09, 2012 11:39 PM To: [email protected] Subject: Re: Coot Book of the Genesis Bernhard, the CentOS5 binaries used to work well on RHEL6 /CentOS6/ SL6 ; there was a glitch a few weeks ago which was fixed after I reported it ( https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=coot;31d9d7f5.1201 ). I install the latest nightly build every couple of months / weeks, and this works very well. So for those who are not interested in learning to build coot (including me) the binaries are the way to go. If the CentOS5 binary needs libraries on RHEL6 /CentOS6/ SL6 , this can be fixed in the way that applies to all s/w packages: from the error message, find the name of the library; yum install <thatlibrary>; repeat until success. Works very well, even with a mix of 32bit and 64bit libraries. good luck, Kay
