Hi, Actually, cctbx on linux has two different built, because different linuxes use different python unicode convention (ucs and utf) therefore, since ccbtx and phaser got some python modules built. They originally are in $CCP4/lib-ucs and $CCP4/lib-utf, but they are not inside $CCP4/lib. The same applies for $CCP4/src/phaser which is also split with ucs, utf tags. If you used install.sh, the script would have performed some check on your machine to detect which unicode convention your python is using and would then automatically moved the appropriate phaser / cctbx at the proper location. If you do not use install.sh then you have to do the check by yourself.
Hope this can help Francois Remacle CCP4 -----Original Message----- From: CCP4 bulletin board [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 20 April 2007 09:45 To: CCP4BB@JISCMAIL.AC.UK Subject: [ccp4bb] further inconsistencies (was: tcltkblt and python distributions) Dear ccp4 developers, when trying to do a conventional install of ccp4 (i.e. avoiding the install.sh script), I ran across additional problems/inconsistencies with the package: 1. In the tarball I freshly downloaded this morning, the cctbx tree under ccp4-6.0.2/lib was completely missing!!! 2. The BINARY.setup script checks for src/phaser, which does not exist (instead there are phaser-ucs and phaser-utf directories). Simply creating the phaser directory may resolve this, but of course the phaser installation is corrupted due to the missing cctbx files. It would be nice if the responsible persons could comment on this. Is the conventional install no longer supported or not even checked? Greetings Oliver ------------------------------- Dr. Oliver H. Weiergraeber Institute of Neurosciences and Biophysics Molecular Biophysics Research Centre Juelich D-52425 Juelich Germany Phone: +49-2461-612028 Fax: +49-2461-612020 -------------------------------
