FreeTDS Development Group

["Ed Ahlsen-Girard" <Ed.Ahlsen-girard AT tybrin.com>]

I'll try grabbing the devel package then, since there appear to be some
quirks in the way yum installed in the first place.

>-----Original Message-----
>From: freetds-bounces AT lists.ibiblio.org
[mailto:freetds-bounces AT lists.ibiblio.org] On Behalf Of Bort, Paul
>Sent: Friday, June 02, 2006 8:22 AM
>To: FreeTDS Development Group
>Subject: Re: [freetds] Don't know what to tell Makefile.PL for
DBD::Sybaseon Centos
>
>I can confirm that you cannot successfully build DBD::Sybase against
FreeTDS without either (a) a complete install from source, or (b) the
freetds-devel package if installing from RPMs. It has to have the header
files. 
>
>
>
>> -----Original Message-----
>> From: freetds-bounces AT lists.ibiblio.org 
>> [mailto:freetds-bounces AT lists.ibiblio.org] On Behalf Of James K. 
>> Lowden
>> Sent: Thursday, June 01, 2006 10:16 PM
>> To: FreeTDS Development Group
>> Subject: Re: [freetds] Don't know what to tell Makefile.PL for 
>> DBD::Sybase on Centos
>> 
>> Ed Ahlsen-Girard wrote:
>> > 
>> > My results were:
>> > 
>> > ldd $(command -v freebcp)
>> >         libsybdb.so.5 => /usr/lib/libsybdb.so.5 (0x0059b000)
>> >         libc.so.6 => /lib/tls/libc.so.6 (0x0032e000)
>> >         /lib/ld-linux.so.2 (0x00315000)
>> > 
>> > My results from env SYBASE=/usr perl ./Makefile.PL are:
>> > 
>> > Can't find the Client Library include files under /usr at
>> ./Makefile.PL
>> > line 129, <IN> line 44.
>> > 
>> > Any reason that using bash would foul this up?
>> 
>> OK, that's progress of a kind.  And no, I don't think bash is the 
>> problem.
>>  
>> 
>> The message is quite clear: the build can't find the "client library 
>> include files".  Those would be the header files.  Behold:
>> 
>> $ ls /usr/local/include/ct*
>> /usr/local/include/ctlib.h              
>> /usr/local/include/ctpublic.h
>> 
>> There are others besides.  Yours of course should be in /usr/include.

>> That would help a bunch.  (If they're there, then I don't know what 
>> could be wrong.)
>> 
>> Is it possible you need some kind of devel package?  If I knew for 
>> sure you were missing only the .h files, I'd suggest you download and

>> build the source tarball, and copy them to /usr/include.  But I don't

>> know what else might be missing.
>> 
>> --jkl