Hi. I ask to add 'mysql', 'unixODBC' and 'myodbc' libraries to 32bit compat for possibility reception to export the data from the wine to mysql under Linux over myodbc-unixODBC link. Thanks. Reproducible: Always
If I don't misremember, app-emulation/wine doesn't RDEPEND on any database, what errors are you getting without them?
Look at: http://www.winehq.org/docs/wineusr-guide/misc-things-to-configure -- quote --------------------------------------------------------------------- 4.3.6.1. Configuring ODBC on Unix The first step in using a Unix ODBC system with Wine is, of course, to get the Unix ODBC system working itself. This may involve downloading code or RPMs etc. There are several Unix ODBC systems available; the one the author is used to is unixODBC (with the IBM DB2 driver). There is also and ODBC-ODBC bridge that can be used to access a Microsoft Access database. Typically such systems will include a tool, such as isql, which will allow you to access the data from the command line so that you can check that the system is working. The next step is to hook the Unix ODBC library to the wine built-in odbc32 DLL. The built-in odbc32 (currently) looks to the environment variable LIB_ODBC_DRIVER_MANAGER for the name of the ODBC library. For example in the author's .bashrc file is the line: export LIB_ODBC_DRIVER_MANAGER=/usr/lib/libodbc.so.1.0.0 If that environment variable is not set then it looks for a library called libodbc.so and so you can add a symbolic link to equate that to your own library. For example as root you could run the commands: $ ln -s libodbc.so.1.0.0 /usr/lib/libodbc.so $ /sbin/ldconfig The last step in configuring this is to ensure that Wine is set up to run the built-in version of odbc32.dll, by modifying the DLL configuration. This built-in DLL merely acts as a stub between the calling code and the Unix ODBC library. If you have any problems then you can use WINEDEBUG=+odbc32 command before running wine to trace what is happening. One word of warning. Some programs actually cheat a little and bypass the ODBC library. For example the Crystal Reports engine goes to the registry to check on the DSN. The fix for this is documented at unixODBC's site where there is a section on using unixODBC with Wine. -- end quote ----------------------------------------------------------------- Thx.
Then need other 32bit sql drivers for unixODBC. PostgreSQL, SQLite.. etc
Shouldn't those also be added as USE/RDEPENDs to wine?
This was solved in app-emulation/emul-linux-x86-db About wine, please open a different bug as I have no idea how wine ebuild handles this optional deps
