Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 10.0.8
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Environment:Linux 2.6.32-431.3.1.el6.x86_64
Description
Centos 6 has libodbc.so.2. But ha_connect.so in bintar is looking for libodbc.so.1.
This means the CONNECT engine is not available at all when using the bin tar on CentOS/RHEL 6.
MariaDB from a yum repo requires libodbc.so.2, which is provided for by Centos 6.x libraries:
[root@localhost ~]# ldd /usr/lib64/mysql/plugin/ha_connect.so linux-vdso.so.1 => (0x00007fffeaf62000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f7e158e4000) libz.so.1 => /lib64/libz.so.1 (0x00007f7e156ce000) libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x00007f7e1537b000) libodbc.so.2 => /usr/lib64/libodbc.so.2 (0x00007f7e15114000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f7e14e0e000) libm.so.6 => /lib64/libm.so.6 (0x00007f7e14b89000) libc.so.6 => /lib64/libc.so.6 (0x00007f7e147f5000) /lib64/ld-linux-x86-64.so.2 (0x00000039dd000000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f7e145f1000) libltdl.so.7 => /usr/lib64/libltdl.so.7 (0x00007f7e143e7000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f7e141d1000)
However, the version of ha_connect from the binary tar (non-glibc 2.14+ version for CentOS/RHEL 6) i.e. mariadb-10.0.8-linux-x86_64.tar.gz,is looking for libodbc.so.1:
[root@localhost ~]# ldd /media/sf_rbensley/Downloads/mariadb-10.0.8-linux-x86_64/lib/plugin/ha_connect.so linux-vdso.so.1 => (0x00007fffcbdff000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f67df717000) libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x00007f67df3c5000) libodbc.so.1 => not found libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f67df0be000) libm.so.6 => /lib64/libm.so.6 (0x00007f67dee3a000) libc.so.6 => /lib64/libc.so.6 (0x00007f67deaa5000) /lib64/ld-linux-x86-64.so.2 (0x00000039dd000000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f67de8a1000) libz.so.1 => /lib64/libz.so.1 (0x00007f67de68b000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f67de474000)
System Info:
[root@localhost ~]# uname -a Linux localhost.localdomain 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 21:39:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
What can we do as a "fix" ? We cannot link with libodbc.so.2 in bintars. We cannot provide third bintar package that would be exactly the same as the second one, but only with libodbc.so.2.
I cannot think or any reasonable thing we could do about this issue.
If you can suggest a solution for this issue feel free to reopen it.
The RPM's for CentOS/RHEL 6 point to the correct libodbc library by default.
Current fix: