FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: RWilbert AT exchange.webmd.net [mailto:RWilbert AT exchange.webmd.net]
> Sent: October 31, 2002 2:28 PM
> 
> Thanks for the quick response.

My pleasure.  

> bash-2.05# ls -l /usr/local/freetds/lib
> total 3832
> -rwxr-xr-x   1 root     system    630040 Oct 31 12:39 libct.a
> -rwxr-xr-x   1 root     system       687 Oct 31 12:39 libct.la
> -rwxr-xr-x   1 root     system    731428 Oct 31 12:39 libsybdb.a
> -rwxr-xr-x   1 root     system       702 Oct 31 12:39 libsybdb.la
[...]

OK, so "make install" is copying the static libraries and not the shared
ones.  

Hmm.  The only thing you did that I've never done is "--enable-shared".  I
wonder if perhaps that's getting in your way.  The syntax help:

  --enable-shared=PKGS  build shared libraries default=yes

is weird.  "PKGS" doesn't usually stands for "yes/no", and "yes" is a funny
name for a package. :/

Why don't you just remove it from your configure invocation, and see what
happens?  This for sure: you don't need it.  

> I added /usr/local/freetds/lib to the LD_LIBRARY_PATH and 
> that did not help.

Well, no, it wouldn't, because the shared libraries aren't there.  

> I tried coping the *.so.o files to $SYBASE/lib/*.so (Poke It 
> With A Stick) and that also failed. 

"make install" does more than just copy the files.  I don't know every
detail, but symbolic links and chmod are two things it does.  

Just to be clear, $SYBASE isn't used by FreeTDS in your setup.  It might be
used by something looking for Sybase libraries (for which FreeTDS likes to
substitute).  

HTH.

--jkl



The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above.  If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that we do not accept account orders and/or
instructions by e-mail, and therefore will not be responsible for carrying
out such orders and/or instructions.