Red Hat 6.4 can't install filePro 5.7.3 - missing libodbc.so.1

[Fairlight]

On Wed, Apr 10, 2013 at 11:31:10AM -0400, Mike Schwartz thus spoke:
>     I'm setting up a brand new 64-bit Red Hat Enterprise version 6.4
>     server.  The Red Hat installation went smoothly, but one of the
>     32-bit apps I'm trying to install (filePro version 5.7.3) says I need
>     to install the "unix ODBC libraries".

Why did they do this?  ODBC has been a Windows-only thing since it was
introduced.  Are they officially supporting it on Linux now?  If not, this
is an absurd bug/glitch on their end.

>      I went to the Red Had Software updates and typed in "libodbc" and
>      it popped up with a few RPM's that I could download, including some
>      "ODBC Development" modules.
>
>      I installed what I thought were some of the most relevant RPMs,
>      including a couple that said "ODBC Development on them).  All the
>      RPMs said "x86_64".  I rebooted and then tried reinstalling filepro,
>      but it still balked at the installation.

*cringe* Seriously?  You do -not- need to reboot after installing
libraries.  You simply run `ldconfig` to refresh the dynamic linker's
knowledge of what is available and where.

>      I was told to look for a library named "/usr/lib/libodbc.so.1",
>      and if it is not there, then I don't have the correct Unix ODBC
>      libraries installed.  All of the ODBC RPM's I installed seemed to
>      have put their libraries into /usr/lib64, so I presume I'm only
>      loading 64-bit libODBC libraries.
>
>      Any suggestions?

On CentOS 6.4 (the downstream carbon copy of RH 6.4) 64-bit,
/usr/lib/libodbc.so.2 is provided by the unixODBC package.  There is
no .so.1 versioned library.  Sounds like fP-Tech linked against an old
version.

You could try installing it and symlink from .so.2 to .so.1, then running
ldconfig.  I give that...eh, about a 5% chance of actually solving the
problem, since APIs usually change between major library versions, not to
mention symbol differences in the library itself that will probably collide
like mad.  But it's your best shot without getting fP-Tech to recompile
on this platform, or without finding out -exactly- which major version of
UnixODBC they built against and rolling a parallel install.  Actually, if
the symlink route fails (almost guaranteed to, but I'd try anyway), doing a
parallel install of an older UnixODBC is probably the sanest thing to do.
Just make sure you toss /usr/local/lib into /etc/ld.so.conf and then run
ldconfig after building and installing it.

The biggest hassle in this is really going to be finding out what version
of it compiles and links to .so.1 instead of .so.2.  The rest is pretty
trivial.

mark->
-- 
Audio panton, cogito singularis.