> Ah, clearly you have done *zero* testing with this package, because
> DBD-Sybase 1.09 fails to build at all with FreeTDS 0.82.
I have not made intensiv testing but the following patch allows
DBD-Sybase-1.09 to build.
The mainstream maintainer don't seems to test with freetds libraries at
all, since the last version able to build on debian is
DBD-Sybase-1.04.
For 1.05 an Experimental Bulk-Load Functionality was added, and since
that time the build don't work if you don't have the Sybase SDK
installed.
The makefile try to disable the functionality if libblk.a is not found
at builtime but don't do it correctly because the Header files delivered
with freetds-dev don't have BLK_VERSION_120/125/150 correctly
defined.
The following proposed patch try to disable the Bulk-Load functionality
correctly.
Anyway the heuristic to look at libblk.a at built time is broken because
as far as I anderstand it, new version of freetds is now having this
functionality but don't have a libblk.a file.
I will fill a bugreport upstream and try to have it tested...
--- dbdimp.c 2009-09-25 15:23:41.000000000 +0200
+++ dbdimp.c.orig 2009-09-25 17:50:28.000000000 +0200
@@ -772,7 +772,6 @@
if (retcode != CS_SUCCEED)
croak("DBD::Sybase initialize: cs_ctx_alloc(%d) failed",
cs_ver);
-#if !defined(NO_BLK)
#if defined(CS_VERSION_150)
if(cs_ver == CS_VERSION_150)
BLK_VERSION = BLK_VERSION_150;
@@ -789,7 +788,6 @@
if(cs_ver == CS_VERSION_110)
BLK_VERSION = BLK_VERSION_110;
#endif
-#endif
if (cs_ver == CS_VERSION_100)
BLK_VERSION = BLK_VERSION_100;
----------------------------------------------
Bye, Raphael.
--
Raphael Descamps
Linux Hosting Backend Solutions
Master of ShaHoLin and Cash Cow Milker
1&1 Internet AG
phone://49.721.91374.0 Brauerstrasse 48
fax://49.721.91374.225 76135 Karlsruhe
Amtsgericht Montabaur HRB 6484 * Vorstand: Henning Ahlert, Ralph Dommermuth,
Matthias Ehrlich, Andreas Gauger, Thomas Gottschlich, Matthias Greve, Robert
Hoffmann, Markus Huhn, Achim Weiss
* Aufsichtsratsvorsitzender: Michael Scheeren
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
