Red Hat Bugzilla – Bug 180143
Old driver path in odbcinst.ini
Last modified: 2013-07-02 23:07:34 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ko; rv:184.108.40.206) Gecko/20060111 Firefox/220.127.116.11
Description of problem:
/etc/odbcinst.ini has old postgresql odbc driver path. new version of odbc driver is /usr/lib64 in FC5.x86_64!!
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. cat /etc/odbcinst.ini
2. ls /usr/lib/libodbc*
Actual Results: result of 1.
# Example driver definitinions
# Included in the unixODBC package
Description = ODBC for PostgreSQL
Driver = /usr/lib/libodbcpsql.so
Setup = /usr/lib/libodbcpsqlS.so
FileUsage = 1
# Driver from the MyODBC package
# Setup from the unixODBC package
#Description = ODBC for MySQL
#Driver = /usr/lib/libmyodbc.so
#Setup = /usr/lib/libodbcmyS.so
result of 2.
ls: /usr/lib/libodbc*: No such file or directory
Expected Results: New postgresql odbc driver for x86_64 is /usr/lib64 and has new name - psqlodbc.so
postgresql-odbc rpm has to change new driver path.
It's not possible to simply change this to /usr/lib64, because the contents of
/etc/odbcinst.ini have to be the same in the 32- and 64-bit RPMs (else there's a
conflict when both are installed on the same machine).
Ulrich Drepper suggested that it might work to say
Driver = $ORIGIN/libodbcpsql.so
Apparently $ORIGIN is a magic token recognized by dlopen() that effectively
means "same directory the calling library is in". Would you check and see
if that helps for you?
Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer
test releases. We're cleaning up the bug database and making sure important bug
reports filed against these test releases don't get lost. It would be helpful if
you could test this issue with a released version of Fedora or with the latest
development / test release. Thanks for your help and for your patience.
[This is a bulk message for all open FC5/FC6 test release bugs. I'm adding
myself to the CC list for each bug, so I'll see any comments you make after this
and do my best to make sure every issue gets proper attention.]
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there have not been any
updates to the report since thirty (30) days or more since we
requested additional information, we're assuming the problem
is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.
Setting status to "INSUFFICIENT_DATA". If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested,
please feel free to reopen the bug report.
Thank you in advance.