Congrats on the official release of 0.5

Curious glitch #1:
=============

I now get the following set of warning messages on every startup:
/sgpp/local/bin/coot/bin/coot-real: /usr/lib/libGL.so.1: no version information 
available (required by /sgpp/local/bin/coot/bin/coot-real)
/sgpp/local/bin/coot/bin/coot-real: /usr/lib/libGL.so.1: no version information 
available (required by /sgpp/local/bin/coot/lib/libgtkgl.so.5)
/sgpp/local/bin/coot/bin/coot-real: /usr/lib/libGL.so.1: no version information 
available (required by /sgpp/local/bin/coot/lib/libglut.so.3)

I've been running various nightly builds of the pre-release for some time now 
without ever getting a message like this.   I doesn't seem to hurt anything, 
but I'm 
wondering what is the cause.

FWIW I get the same warning message from ldd

ldd /sgpp/local/bin/coot-0.5-redhat-8.0/bin/coot-real
/sgpp/local/bin/coot-0.5-redhat-8.0/bin/coot-real: /usr/lib/libGL.so.1: no 
version 
information available (required 
by /sgpp/local/bin/coot-0.5-redhat-8.0/bin/coot-real)


Curious glitch #2:
==============

Hitting the "about" button and selecting either "Coot News" or "About" produces 
the following error trace (again this was working in the pre-release version).

n /sgpp/local/bin/coot/share/guile/gtk-1.2/gtk.scm:
 127: 0* [apply #<procedure #f ()> ()]
In unknown file:
   ?: 1  [#<procedure #f ()>]
In /sgpp/local/bin/coot/share/coot/scheme/coot-gui.scm:
   ...
2279: 2  (let (# # # # ...) (set! text-1 #) (set! text-2 #) ...)
2309: 3* [coot-news-info get-news]
In unknown file:
   ?: 4  (letrec (# # # # ...) (cond # #))
   ...
   ?: 5  [get-news]
In /sgpp/local/bin/coot/share/coot/scheme/coot-gui.scm:
2213: 6  (set! thread (call-with-new-thread get-news-thread 
coot-news-error-handler))
2213: 7* (call-with-new-thread get-news-thread coot-news-error-handler)
/sgpp/local/bin/coot/share/coot/scheme/coot-gui.scm:2213:22: In expression 
(call-with-new-thread get-news-thread coot-news-error-handler):
/sgpp/local/bin/coot/share/coot/scheme/coot-gui.scm:2213:22: Unbound variable: 
call-with-new-thread

Reply via email to