Dear Gina:

I think Coot 0.0.33 originated sometime early in the Nixon administration, and 
I finally parted with my SGIs a few years ago, so am not in a good position to 
advise.  I seem vaguely to remember some non-canonical naming of the files.  
What happens if you make a symbolic link from the one you have to the one that 
is required?

As I recall, coot on an SGI (at least on my R10000, which I think has a 
processor almost as fast as that in my generation A iPod touch) was impossibly 
slow.  By contrast, I can run the very latest svn revision of coot in stereo on 
a $270 Zalman monitor attached to a $600 mac mini.

I'm sorry this doesn't answer your question, but I think an ancient version of 
coot on an ancient computer will just be a world of hurt.

-- Bill

William G. Scott
Professor
Department of Chemistry and Biochemistry
and The Center for the Molecular Biology of RNA
228 Sinsheimer Laboratories
University of California at Santa Cruz
Santa Cruz, California 95064
USA
 

On Jan 26, 2012, at 8:59 AM, Clayton, Gina wrote:

> Hi there
> 
> we are trying to install Coot onto one of our old SGIs and so we installed 
> Coot 0.0.33 (IRIX). However when starting Coot,  such as in the Coot 
> (install) directory,  we get an error message stating thatlib "libgcc_s.so is 
> required but can not be found. We have the sgi freeware gcc_lib installed 
> (the link on the Coot page to sgi.freeware, is dead ) but can only find 
> libgcc_a in our gcc_lib. 
> 
> Can someone tell us how we can get hold of the right library?
> 
> Thanks so much for any help
> Gina 
> 
> 
> NOTICE: This email message is for the sole use of the intended recipient(s) 
> and may contain confidential and privileged information. Any unauthorized 
> review, use, disclosure or distribution is prohibited. If you are not the 
> intended recipient, please contact the sender by reply email and destroy all 
> copies of the original message.

Reply via email to