On Thursday 19 of May 2005 02:13, Christian Hammers wrote: > > This bug is even worse. It seems there is name clash with library symbols > > betweent statically linked db3 in mysql and shared linked db3 (or db4.3) > > in nss_db. I'm sure it is the reason that mysql doesn't work with > > nss_ldap, too. > > > > I see a few solutions: > > > > 1. Drop bdb support in mysql at all. It might be a backward compatibility > > problem but I think it could be conditionally compiled, like static > > linking already. > > I would go for this one, too. Can you confirm that the problem is only > present in 4.1 and not in mysql-server 4.0? I could not reproduce it there.
My yesterday research: The current libnss-db linked with libdb3 crashes only mysql-server-4.1. The solution might me to build bundled libdb4.3 from mysql-server-4.1 package with "--with-uniquename=_mysql" option. The patch is a little tricky and I'm preparing it already. Unfortunately, libnss-db linked with libdb4.3 (it might be in future) crashes mysql-server 4.0 and there is no solution for avoid name symbols clash. The most safe solution would be to remove bdb support. If it is not possible, please consider to compile mysql-server-4.1 with additional patch which I could prepare for you, but we will be in trouble after library changes in libnss-db. -- .''`. Piotr Roszatycki, Netia SA : :' : mailto:[EMAIL PROTECTED] `. `' mailto:[EMAIL PROTECTED] `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
