after installing the dbddesigner is simply start as user the dbdesigner script to startup. when i try to connect to the mysql database then i get the error you can see above on the url. in the forum from dbddesigner it gives a thread but no has help me: http://www.fabforce.net/forum/viewtopic.php?t=1025&highlight=libmysqlclient Reproducible: Always Steps to Reproduce: 1. choose in the menu on top "Database" 2. choose the connection you have setup 3. click connect
Emerged MySQL 4.0.23-r1, and after that postfix stopped working. I got the following error message: postfix: error while loading shared libraries: libmysqlclient.so.12: cannot open shared object file: No such file or directory Turns out there is no such file any longer. There also is no libmysqlclient.so file. Trying to re-emerge postfix lands me the error: ld: cannot find -lmysqlclient Downgrading to 4.0.22 again, and seeing if that fixes the problem.
Noted this after a tear-my-hair-out problem with what I thought was QT: Making install in tools make[1]: Entering directory `/var/tmp/portage/mysql-4.0.23-r1/work/mysql-4.0.23/tools' make[2]: Entering directory `/var/tmp/portage/mysql-4.0.23-r1/work/mysql-4.0.23/tools' test -z "/usr/bin" || mkdir -p -- . "/var/tmp/portage/mysql-4.0.23-r1/image//usr/bin" /bin/sh ../libtool --preserve-dup-deps --mode=install /bin/install -c 'mysqlmanager' '/var/tmp/portage/mysql-4.0.23-r1/image//usr/bin/mysqlmanager' libtool: install: warning: `../libmysql_r/libmysqlclient_r.la' has not been installed in `/usr/lib/mysql' /bin/install -c .libs/mysqlmanager /var/tmp/portage/mysql-4.0.23-r1/image//usr/bin/mysqlmanager make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/var/tmp/portage/mysql-4.0.23-r1/work/mysql-4.0.23/tools' make[1]: Leaving directory `/var/tmp/portage/mysql-4.0.23-r1/work/mysql-4.0.23/tools' mv: cannot stat `/var/tmp/portage/mysql-4.0.23-r1/image//usr/lib/mysql/libmysqlclient*.so*': No such file or directory ^^^ Note the last line above and the "No such file or directory" at the end of it.
I should note that, obviously, this is a problem with the dev-db/mysql-4.0.23-r1 ebuild. I'm masking it and going back to 4.0.22, as well.
comparing a working system to one with this problem, it appears that the files in lib no longer include the .so extension: good: libmysqlclient.so libmysqlclient.so.12 libmysqlclient.so.12.0.0 broken: libmysqlclient libmysqlclient.12 libmysqlclient.12.0.0
There was some nasty bug in mysql 4.0.23-r1. I think -r2 fixes all known bugs.
Using mysql-4.0.23-r2, I experience the same as with mysql-4.0.23-r1; There are no libmysqlclient*.so's in /usr/lib and revdep-rebuild'ing fails for packages depending on mysql. Oddly enough: bluebird mysql # qpkg -I -v mysql dev-db/mysql-4.0.23-r2 * dev-perl/DBD-mysql-2.9003 * bluebird mysql # qpkg -I -l mysql | grep mysqlclient.so /usr/lib/mysql/libmysqlclient.so -> ../libmysqlclient.so 1106270311 bluebird mysql # ls -l /usr/lib/mysql/libmysqlclient.so ls: /usr/lib/mysql/libmysqlclient.so: No such file or directory bluebird mysql # ls -l /usr/lib/libmysqlclient.so ls: /usr/lib/libmysqlclient.so: No such file or directory
$ qpkg -f -v /usr/lib/libmysqlclient.so dev-db/mysql-4.0.23-r2 * I'll try to use dbdesigner tomorrow and test it out.
MySQL 4.0.25-r2 is now stable on x86 and amd64
