https://bugs.documentfoundation.org/show_bug.cgi?id=65830

--- Comment #41 from Beluga <[email protected]> ---
(In reply to Lionel Elie Mamane from comment #40)
> The "Driver = ..." line must match the section name in odbcinst.ini (where
> you put "unixODBC" which is a bit weird). In other words, the Driver line in
> my instructions assumes that the corresponding driver section is called
> "MySQL", but you called it "unixODBC". Also, it seems unusual to me that the
> "Setup = " line maps to unixodbc's libodbcinst.so instead of a myodbc .so
> file; my entry has "Setup=libodbcmyS.so"; that's on Debian GNU/Linux FWIW.
> 

Ok I made the change to MySQL, no help.

I don't have any libodbcmyS.so in /usr/lib64 or anywhere in this system.

Note that I haver never done this before, have no personal use for this and I'm
only doing this for QA testing. I'm using an openSUSE VM specifically set up
for testing this report.

> This sounds like LibreOffice is compiled for a different libodbc than what
> you have... Usually, when the .so has a different name, it means it is an
> incompatible version, and simply linking one to the other WILL NOT WORK (or
> can seem to work, but lead to crashes, data corruption, etc).

I'm using TDF's build:
Version: 4.4.0.3
Build ID: de093506bcdc5fafd9023ee680b8c60e3e0645d7

I found this: http://www.unixodbc.org/
28.Nov.2011     2.3.1 Released

Mainly bug fixes.
Major change is to change the library version number from 1 to 2 to signal the
SQLLEN change for 64 land. Should have been done for 2.3.0, but better late
than never. So if after installing you have apps that can't find libodbc.so,
its likely they are linked to libodbc.so.1, so just create a symlink from
libodbc.so.2 
----------

Based on that official suggestion to symlink, there seems to be no danger.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to