Hi,
I think the MSDBLIB macro was for use with Microsoft's DBlibrary implementation (which may not even exist anymore).
I think you should take this up on the freetds mailing list - I haven't touched the Sybase::DBlib code in ages and I really don't remember what the problems were...
Thanks,
Michael
-----Original Message-----
From: owner-sybperl-***@peppler.org [mailto:owner-sybperl-***@peppler.org] On Behalf Of Ed Avis
Sent: Friday, July 24, 2009 12:20 PM
To: Michael Peppler
Cc: sybperl-***@peppler.org
Subject: RE: Sybperl and FreeTDS and MSSQL
Post by Michael PepplerSybase::DBlib will certainly work with FreeTDS.
In that case my follow-up question is about this build error:
DBlib.xs: In function 'XS_Sybase__DBlib__DateTime_crack':
DBlib.xs:6068: error: 'DBDATEREC' has no member named 'dateyear'
DBlib.xs:6069: error: 'DBDATEREC' has no member named 'datemonth'
DBlib.xs:6070: error: 'DBDATEREC' has no member named 'datedmonth'
Looking at the file DBlib.c (which I assume is generated from DBlib.xs) there is
a definition for DBDATEREC, but it is inside a #ifndef DBBOTH conditional. The
definition that's used is from /usr/include/sybdb.h, which has
typedef struct dbdaterec
{
#ifdef MSDBLIB
DBINT year;
DBINT month;
DBINT day;
DBINT dayofyear;
DBINT weekday;
DBINT hour;
DBINT minute;
DBINT second;
DBINT millisecond;
DBINT tzone;
#else
DBINT dateyear;
DBINT datemonth;
DBINT datedmonth;
DBINT datedyear;
DBINT datedweek;
DBINT datehour;
DBINT dateminute;
DBINT datesecond;
DBINT datemsecond;
DBINT datetzone;
#endif
} DBDATEREC;
I suppose MSDBLIB is defined for some reason? Does DBlib.xs need adapting to
build with this set?
--
Ed Avis <***@waniasset.com>
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to European legal entities.