Dear All,
I have to apologize for my somewhat insinuating message about CCP4
behavior. In order to retain command line functionality of CCP4
programs, I always sourced CCP4 setup script in my bashrc file, and this
is what caused a significant amount of grief for me later. However,
sourcing CCP4 setup is unnecessary for the ccp4i interface, which is
self-consistent and fully contained in terms of environmental variables,
and this is how we are supposed to use CCP4 today anyway.
Sincerely,
Petr
P.S. Many thanks to Ed Pozharski for giving me pointers to figure out
this "problem".
On 03/12/2015 08:49 PM, Petr Leiman wrote:
> Dear Community,
>
> What is the reason of placing the CCP4 PATH and other path-related variables in front of existing variables? This forces a linux system to use CCP4-distributed wish in all applications by default. Note that the ccp4i script calls CCP4 distributed wish explicitly with its full path.
>
> This might be trivial, and the fix is also trivial, but trivial things like that cause a lot of lost time and head scratching when tcl/tk programs compile without errors and perform some operations correctly but segfault on others - all due to a mixup of libraries and wish executables caused by CCP4 wish.
>
> Would it be possible to append CCP4 path variables by default instead of rather rudely jumping in front of the queue?
>
> Thank you,
>
> Petr
>
> ------------------
> Petr Leiman
> EPFL
> BSP 415
> CH-1015 Lausanne
> Switzerland
> Office: +41 21 69 30 441
> Mobile: +41 79 538 7647
> Fax: +41 21 69 30 422
> http://lbbs.epfl.ch
|