FreeTDS Development Group

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

> From: david_e_holsinger AT bankone.com
> Sent: August 1, 2003 12:07 PM
> 
> Preparing a Red Hat 8.0 workstation to access MSSQL databases 
> using perl.
> Have installed freeTDS v.61 (rpm).  Verified it talks to the MSSQL
> databases via sqsh.  Trying to install DBD-Sybase-1.00.  "make" of
> DBD-Sybase fails consistantly.  Have followed instructions in 
> all README.

What says "grep CS_SMALLINT $SYBASE/include/cspublic.h"?

It looks like $SYBASE isn't pointed to /usr/local/freetds (or wherever
FreeTDS is installed).  From the DBD::Sybase README:

"This version attempts to find out which libraries it needs by looking
at $SYBASE/lib ($SYBASE/$SYBASE_OCS/lib for ASE 12.x installations.)
... It assumes that $SYBASE is set and points to
the Sybase installation directory that you want to use to build
DBD::Sybase."

HTH.

--jkl

> gcc -c  -I/usr/include
> -I/usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/auto/DBI
> -D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -D_LARGEFILE_SOURCE
> -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm -O2 -march=i386 -mcpu=i686
> -DVERSION=\"1.00\" -DXS_VERSION=\"1.00\" -fpic "
> -I/usr/lib/perl5/5.8.0/i386-linux-thread-multi/CORE"   Sybase.c
> cc1: warning: changing search order for system directory 
> "/usr/include"
> cc1: warning:   as it has already been specified as a 
> non-system directory
> In file included from Sybase.xs:14:
> Sybase.h:16:22: ctpublic.h: No such file or directory
> In file included from Sybase.h:46,
>                  from Sybase.xs:14:
> dbdimp.h:23: parse error before "CS_SMALLINT"
-----------------------------------------
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.