On 08/08/2023 06:49, Edward A. Berry wrote:
> I would appreciate instruction for getting a downloaded coot binary to
> run.


Fair enough.


The idea is that you untar the binary tar file and put
/somewhere/coot-something/bin in your PATH. That's it. You shouldn't
need to edit any coot files. Coot is compiled and distributed with its
own python, so setting PYTHON to the system one will upset it, because
the system python doesn't know about the coot module.


Keeping on top of making binaries is the majority of a full-time job
itself and I just have not been able to manage it. I can make binaries
for the computers I use that are connected to the internet - i.e. the
Scientific Linux build. Maybe one day things will change. But at the
moment it's just sad times. The options are, pick it up from CCP4 or
compile it yourself.


Regards,


Paul.



> I got coot-0.9.7-binary-Linux-x86_64-centos-7-python-gtk2.tar.gz
> There is no README file in the top directory.
> I edited bin/coot to set
> #PYTHON=/tb2/sw/lnx/coot-Linux-x86_64-centos-7-gtk2-python/include/python2.7
> #PYTHON=/usr/bin/python2.7
> PYTHON=/usr/lib64/python2.7
>
> With or without those edits, it runs as far as bringing up the
> graphics screen, loading the standard residues, and saying hello- then
> crashes with:
> (set-display-lists-for-maps 1)
> Stack trace (most recent call last):
> #0    Object
> "/tb2/sw/lnx/coot-Linux-x86_64-centos-7-gtk2-python/lib/libgmp.so.10",
> at 0x7f3097b3133b, in __gmpn_mul_1
> Illegal instruction (Illegal operand [0x7f3097b3133b])
> /sw/lnx/coot-Linux-x86_64-centos-7-gtk2-python/bin/coot: line 264:
> 10999 Illegal instruction     (core dumped) $coot_bin "$@"
> (more below)
>

########################################################################

To unsubscribe from the COOT list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/WA-JISC.exe?SUBED1=COOT&A=1

This message was issued to members of www.jiscmail.ac.uk/COOT, a mailing list 
hosted by www.jiscmail.ac.uk, terms & conditions are available at 
https://www.jiscmail.ac.uk/policyandsecurity/

Reply via email to