On 14/06/2016 15:49, Frank Eisenmenger wrote:
> I was asked to install 'coot' on a Linux box (Fedora 23).
>
> 1) after 'tar xvzf
> coot-0.8.4-pre-revision-6068-binary-Linux-x86_64-rhel-6-python-gtk2.tar.gz',
>
>I noticed, that ALL sub-directories were NOT ACCESSIBLE for all other >
users (except the one who unpacked the archive), as well as some
> files - most importantly the *.cif below <path>/coot-Linux-x86_64-
> rhel-6-gtk2-python/share/coot/lib/data/monomers/
>
> How can I avoid this in order to make 'coot' usable for other users,
> too ?
I think that the latest tar has this fixed.
http://www2.mrc-lmb.cam.ac.uk/personal/pemsley/coot/binaries/pre-releases/coot-0.8.4-pre-revision-6073-binary-Linux-x86_64-rhel-6-python-gtk2.tar.gz
>
>
> 2) after installing some missing pre-requisites ( gtk2-devel,
> libgnomecanvas-devel, pangox-compat-devel ), I tried to compile
> 'coot' using
> https://raw.githubusercontent.com/pemsley/coot/master/build-it
good :-)
> The compilation with './build-it python' seems to have been
> successful, but trying (with previously: export
> LD_LIBRARY_PATH=$HOME/autobuild/building/ataraxia_2016-06-14__T07_54_19/coot-0.8.4-pre/lib
> )
Hmmm... you shouldn't need to do that to build coot. Are you saying that
you needed to do so?
>
> sh
> $HOME/autobuild/building/ataraxia_2016-06-14__T07_54_19/coot-0.8.4-pre/src/coot
>
> NO
> $HOME/autobuild/building/ataraxia_2016-06-14__T07_54_19/coot-0.8.4-pre/libexec/coot-bin
> & <path>/bin/guile could be found - i.e. there were NO sub-dirs
> <path>/libexec/ & <path>/bin/
>
> From this, I concluded, that the installation did not reach its final
> stage - How should I continue ?
>
Have a look in $HOME/autobuild/Linux-*/bin
There should be a coot there. The idea is to put the above directory in
your path.
Paul.
|