I have RHEL62-64 in a win 7-64 8GB desktop VMware installation. CCP4, ccp4i,
coot, and shelxcde beta executables run fine.
There were issues with the coot package installation due to unresolved
dependencies
and my ignorance thereof, but I think a working RHEL62-64 compatible package
is available now, the coot wiki has latest info.
I could not get Xtalview running, probably some xterm thing beyond my grasp,
which also screws up the latest hkl2mapV0.3,
V0.2 runs fine. 
Free intel ifort runs great.

The great part about the VM ware installation is that I also got it running
on a win7-64 8GB laptop
by simply copying the virtual RHEL machine (files).
That alone saved a few day's work.
Also the Unity feature of VMware is a blast.

BR

-----Original Message-----
From: CCP4 bulletin board [mailto:CCP4BB@JISCMAIL.AC.UK] On Behalf Of Roger
Rowlett
Sent: Tuesday, April 03, 2012 12:58 PM
To: CCP4BB@JISCMAIL.AC.UK
Subject: [ccp4bb] Who is using 64-bit Linux?

The time has come for me to upgrade my Linux OS to something more recent for
me and my student workstations. A 32-bit distro is certainly conservative
and compatible with CCP4 and Coot, but it seems like that solution hobbles
my hardware and puts some limitations on available memory, even with PAE
enabled. So who is using a 64-bit distro these days, and are there lingering
issues of compatibility and dependency hell with commonly used XRD software,
like CCP4, Coot, iMOSFLM etc.?

Ubuntu 12.04 LTS (beta) actually works OK with one simple workaround for the
global menu for CCP4 and Coot, and wine compatibility is fine for running
CrysalisPro in the same environment, so it's really comes down to whether or
not the extra performance of a 64-bit OS is worth the pain of compatibility
issues for XRD software. Any thoughts?

Cheers,

_______________________________________
Roger S. Rowlett
Gordon & Dorothy Kline Professor
Department of Chemistry
Colgate University
13 Oak Drive
Hamilton, NY 13346

tel: (315)-228-7245
ofc: (315)-228-7395
fax: (315)-228-7935
email: rrowl...@colgate.edu

Reply via email to