[unixODBC-support] configuring to use alternate unixODBC driver
harold at uga.edu
Fri Jan 30 14:24:10 GMT 2015
On 1/22/2015 7:58 PM, Mike wrote:
> Any chance that your HOME or OBDCSYSINI paths are really long?
> It seems you compiled this yourself.
> If you just used the default 'make install' without any parameters, normally it would go to /usr/local.
That's where it is. My problem is I don't know how to tell linux to load it instead of the system version in /usr/lib and /usr/lib64
> If you didn't compile this yourself, use your package manager to tell you where the files will end up.
> Look here for a suggestion: http://www.cyberciti.biz/faq/rhel-centos-fedora-list-contents-of-package-using-yum-command/
> I might be missing something though, so any more info you have that you think could help would be great.
> Mike B.
> Quoting Harold Pritchett <harold at uga.edu>:
>> I am working on troubleshooting a problem with a php program accessing a db2 database under CENTOS 6.
>> I am using the default versions of everything, at the current level. A program which I know works on a system with much down level versions of almost everything instead is
>> failing with a segmentation fault. The purpose of this project is to get the production system to current software levels.
>> As a first step, I downloaded the current version (unixODBC-2.3.2) of the unixODBC driver and built it.
>> Now, I can't find where to tell my system to load this driver instead of the default one from /usr/lib or /usr/lib64
>> my drivers are here:
>> # find / -name libodbc.so -print
>> Thanks for any assistance.
>> unixODBC-support mailing list
>> unixODBC-support at mailman.unixodbc.org
> unixODBC-support mailing list
> unixODBC-support at mailman.unixodbc.org
More information about the unixODBC-support