dbdesigner ODBC drivers and MSSQL drivers not included in ebuild. I don't know if you packaged it like this on purpose, but I have no idea where to get these drivers for dbd and it would be nice if they were included... Reproducible: Always Steps to Reproduce: 1. Start dbdesigner 2. Try connect to a MSSQL database or an ODBC database Actual Results: dbdesigner displayes an error message that states that it can't find the driver Expected Results: connect to database
I cannot see where these plugins are available either. If you can find URIs for them I'll be glad to include them in our package.
I'm not sure it's related, but when I do a revdep-rebuild I got : /opt/DBDesigner4/Linuxlib/libdbxoodbc.so (requires libodbc.so.1 ) For linodbc.so.1, I emerged dev-db/unixODBC and no more problems when doing revdep-rebuild. Drivers for unixODBC may be found there : http://www.unixodbc.org/drivers.html Maybe these should be added as requirement for dbdesigner ebuild ?
It looks like you are right. I confirmed the missing ODBC thing and will add unixODBC as a dep if USE="odbc". I'll let you know when this is in portage. Will be a revision bump. Still no idea on MSSQL drivers. Perhaps I'll sniff around their forums.
ldd shows that, for ODBC, we also need: libborunwind.so.6.0 => not found The forums say this is part of kylix libs, this package is not yet available by source.
I used mandrake binaries (kylixlibs3-unwind-3.0-2mdk.i586.rpm and rpm2targz) to solve libborunwind.so.6.0 problem (don't let revdep-rebuild reemerge dbdesigner), and that's seems OK. But as I don't really know what it is used for ... I can't test if it is a reliable solution.
Created attachment 41962 [details] dbdesigner-4.0.5.4.ebuild I updated the ebuild to make it work on amd64. lib-compat provided by app-emulation/emul-linux-x86-baselibs on amd64 (see bug 55381 and 47786). New dependency: "x86? ( sys-libs/lib-compat ) amd64? ( app-emulation/emul-linux-x86-baselibs )" I also added a remark to ebuild where to fetch a missing library: #According to the following thread #http://www.fabforce.net/forum/viewtopic.php?t=992 #libborunwind.so.6.0 is needed by DBDesigner4-0.5.4 #Get it from the file 602sql-Xconsole-binary-8.1-1.tar.gz #http://www.software602.sk/produkty/602sql/download.php I don't now if it is free and where to place it (/usr/lib32 ?). Anyhow the application still does not start for me ;-(
Created attachment 41963 [details] startdbd.desktop startdbd.desktop did contain the wrong path to the application.
dbdesigner links to it's own libmysqlclient.so.10.0.0 in /opt/DBDesigner4/LinuxLib wich is not compatible with libmysqlclient.so.12.0.0 in /usr/lib. Temporary workaround: cp /usr/lib/libmysqlclient.12.0.0 /opt/DBDEsigner4/LinuxLib cd /opt/DBDesigner4/LinuxLib rm libmysqlclient.so ln -s libmysqlclient.so.12.0.0 libmysqlclient.so
simpler: nhh221 ~ # cd /opt/DBDesigner4/Linuxlib/ nhh221 /opt/DBDesigner4/Linuxlib #ln -sf /usr/lib/libmysqlclient.so.12.0.0 ./libmysqlclient.so
Jorg re-file your request as a separate bug instead of muddying this bug. If you don't have mysql installed, does the dbdesigner-provided lib work?
I'm getting "Invalid Field Type" when trying to connect to MySQL after symlinking to the official mysql lib.
(In reply to comment #9) > simpler: > nhh221 ~ # cd /opt/DBDesigner4/Linuxlib/ > nhh221 /opt/DBDesigner4/Linuxlib #ln -sf /usr/lib/libmysqlclient.so.12.0.0 ./libmysqlclient.so > This is what I do, azrael Linuxlib # ln -sf /usr/lib/libmysqlclient.so.15.0.0 ./libmysqlclient.so but I'm reciving this mesg: Unable to load libmysqlclient.so, when I tried connect to MySQL can any one help?
Reassign wrt Bug 22118
*** Bug 83930 has been marked as a duplicate of this bug. ***
http://bugs.gentoo.org/show_bug.cgi?id=83930#c1 x11-libs/kylixlibs3-borqt also contains the library in the above comment. As kylix installs the lib into /opt/kylix3/, I had to create a symbolic link into /lib. But I guess it would be better to get the library from the package mentioned in the before mentioned comment.
*** Bug 128609 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 135731 ***
