[freetds] CentOS - odbc.ini driver value?
rich at experienceplus.com
Mon Jun 12 11:29:56 EDT 2006
Thanks, James - it appears that the CentOS installation included
unixODBC, but not *really*. When I ran rpm -q on it, it indicated it was
installed - but there wasn't anything except documentation when I looked
in the directories. A little mystifying.
So I cleaned out the prior version of freeTDS, un- and re-installed
unixODBC, reinstalled freeTDS and edited the freetds.conf and odbc.ini
files, and I'm in business. isql run against my DSN works just fine.
(Just got to get PHP's ODBC library working now... but that's a much
less scary problem.)
I'm Rich Young, and I approved this message.
> -----Original Message-----
> From: freetds-bounces at lists.ibiblio.org
> [mailto:freetds-bounces at lists.ibiblio.org] On Behalf Of
> Lowden, James K
> Sent: Friday, June 09, 2006 4:06 PM
> To: FreeTDS Development Group
> Subject: Re: [freetds] CentOS - odbc.ini driver value?
> > I've got a fresh freeTDS 0.63 installation (from source) on CentOS
> > 4.3 that's working fine with tsql, but isql chokes because it can't
> > find the driver.
> > [unixODBC][Driver Manager]Can't open lib
> > : /usr/lib/libtdsodbc.so: cannot open shared object file:
> > No such file or directory
> > Indeed, there's no such file - I copied this setting from
> > the Fedora server I'm replacing. But locate (freshly updated)
> > turns up no libtdsodbc.so filenames anywhere.
> The configure script looks for a driver manager. If it finds
> one, it builds the ODBC driver, else not.
> If you check your build log, I think you'll see it didn't
> find one, probably because it's not installed where the
> scanner looked.
> You can force the issue thus:
> $ ./configure --help | grep unixodbc
> --with-unixodbc=DIR build odbc driver against unixODBC in DIR
> Substitute for DIR the location of your DM. Then make clean;
> make install, and you should be all set.
More information about the FreeTDS