[Zope] Shattered dreams... And glibc

[Shaw, Howard]

Can anyone tell me whether the Zope precompiled binaries are statically
linked or not? 

I'm running a Redhat 5.1 system, and I downloaded the most recent MySQL
rpm, to see if it affected my Zope recurrent death problem at all. In
the upgrade notes in the rpm, it mentions that Redhat 5.1 system's
glibc-2.0.7-13 has a problem that causes some MySQL clients to die of
memory problems. It recommends upgrading to glibc-2.0.7-9, which I am
about to do.

Since I compiled the MySQLmodule for Python directly from the ZMySQLDA
package, on this system with a bad glibc, it seems probable that this
might be my solution. I am going to download the upgraded glibc and
recompile, and will inform the list of the result.

Second question: The newest MySQL rpm, 3.22.16a-gamma-1, implies that
some older client software using certain C calls to connect may need to
be rewritten to work; and indeed, I cannot connect to the newer mysqld
from Zope or PHPMyAdmin, although I can see with 'mysql' that it is
running and does contain the same databases and same data. Any ideas on
what I can do to make these two work together?

This is not a priority issue, since my previous MySQL was installed in
/usr/local from the precompiled statically linked tar.gz, and is still
usable, so once I recompile MySQLDA with the newer glibc, I will
downshift to the older MySQL... But I would like to know how to resolve
the problem with the newer MySQL. 

Thanks for the help.

Howard C. Shaw III
St. Thomas High School
Houston, Texas