[unixODBC-dev] Could we only keep libodbc.so and libodbcinst.so?

Nick Gorham nick.gorham at easysoft.com
Fri Apr 20 07:57:47 BST 2007


Xiong.He at sybase.com wrote:

>
> Hi,
>
> When I finished building the unixODBC in linux/solaris platform, I 
> found that
> the isql cmd line tool library dependency like below:
>
> sean at testlinux:odbc/bin> ldd isql
>         linux-gate.so.1 =>  (0xffffe000)
>         libodbc.so.1 => /odbc/lib/libodbc.so.1 (0x40018000)
>         libodbcinst.so.1 => /odbc/lib/libodbcinst.so.1 (0x40082000)
>         libdl.so.2 => /lib/libdl.so.2 (0x400a9000)
>         libreadline.so.4 => /lib/libreadline.so.4 (0x400ac000)
>         libncurses.so.5 => /lib/libncurses.so.5 (0x400d9000)
>         libpthread.so.0 => /lib/tls/libpthread.so.0 (0x4011e000)
>         libc.so.6 => /lib/tls/libc.so.6 (0x4012e000)
>         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
>
> So if we distribute unixodbc, we have to add softlinks libodbc.so ---> 
> libodbc.so.1
> libodbcinst.so ---> libodbcinst.so.1
>
> Could we add an option to configure.sh to ensure that
>         we just generate libodbc.so and libodbcinst.so?


Feel free to make suce a change, I think you will have to alter libtool, 
Maybe SONAME. Don't forget the cursor lib as well.

Libtool does have valid reasons to do that; though the chance of a API 
change causing a .so.2 is low I guess.

-- 
Nick



More information about the unixODBC-dev mailing list