ODBC driver can't find libodbcinst.so.1.0.0 because symbolic link is missing
Bug #1748508 reported by
Chris Hamilton
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unixodbc (Ubuntu) |
Opinion
|
Undecided
|
Unassigned |
Bug Description
Hello,
I noticed that my driver couldn't find certain symbols in libodbcinst.
I'm currently using Ubuntu 12.04.2 LTS, the unixODBC package version is 2.2.14p2-5ubuntu3.
Regards,
Chris
To post a comment you must log in.
Hi,
while sometimes there are links from <name>.so to <name>.<version>.so for compat reasons that is no hard requirement IMHO.
You are right - it could be added - but anything built on Ubuntu should get the right linkage on the build.
So for example:
linux- vdso.so. 1 => (0x00007fff0efe e000)
libodbcinst. so.1 => /usr/lib/ x86_64- linux-gnu/ libodbcinst. so.1 (0x00007fbcaeb1 f000)
# ldd /usr/bin/odbcinst
Especially with latter releases having multiple sover's I think not having a default link is even better: x86_64- linux-gnu/ libodbcinst. so.1 -> libodbcinst.so.2 x86_64- linux-gnu/ libodbcinst. so.2 -> libodbcinst. so.2.0. 0 x86_64- linux-gnu/ libodbcinst. so.2.0. 0
# ll $(dpkg -L odbcinst1debian2 | grep libodbcinst)
lrwxrwxrwx 1 root root 16 Nov 7 07:12 /usr/lib/
lrwxrwxrwx 1 root root 20 Nov 7 07:12 /usr/lib/
-rw-r--r-- 1 root root 72032 Nov 7 07:12 /usr/lib/
Which "driver" are you referring to that isn't finding it?
We'd need to check why it isn't holding a working linkage info and resolve that IMHO.
incomplete until we know more about the driver to fix it.