Re: [Python-sybase-misc] build on ubuntu8.04

[Sébastien S. <sa...@us...>]

Hi Dave,

CS_DESCRIBE_OUTPUT is not really necessary if you only use the DBAPI 
interface of python-sybase. So I suppose you could try the following patch.

I plan to try Freetds in coming days to see how python-sybase behaves 
with it and if that could be improve. That being said, I think the 
priority is to have something working fine with the original sybase 
version of libraries, so if FreeTDS is not compatible in some way, it 
should be changed to behave like the reference.

regards

--
Sébastien Sablé

Index: cmd.c
===================================================================
--- cmd.c	(révision 443)
+++ cmd.c	(copie de travail)
@@ -612,10 +612,12 @@
  	/* ct_dynamic(CS_DESCRIBE_INPUT, dyn_id) -> status */
  	if (cmd_str == NULL)
  	    cmd_str = "CS_DESCRIBE_INPUT";
+#if 0
      case CS_DESCRIBE_OUTPUT:
  	/* ct_dynamic(CS_DESCRIBE_OUTPUT, dyn_id) -> status */
  	if (cmd_str == NULL)
  	    cmd_str = "CS_DESCRIBE_OUTPUT";
+#endif
      case CS_EXECUTE:
  	/* ct_dynamic(CS_EXECUTE, dyn_id) -> status */
  	if (cmd_str == NULL)
Index: sybasect.c
===================================================================
--- sybasect.c	(révision 443)
+++ sybasect.c	(copie de travail)
@@ -650,9 +650,11 @@
  #ifdef CS_DESCRIBE_INPUT
      SYVAL(VAL_DYNAMIC, CS_DESCRIBE_INPUT),
  #endif
+#if 0
  #ifdef CS_DESCRIBE_OUTPUT
      SYVAL(VAL_DYNAMIC, CS_DESCRIBE_OUTPUT),
  #endif
+#endif
  #ifdef CS_DYN_CURSOR_DECLARE
      SYVAL(VAL_DYNAMIC, CS_DYN_CURSOR_DECLARE),
  #endif



Dave Thiede a écrit :
> I'm trying to build the package on a 64bit install of ubuntu 8.04 against 
> freetds-dev 0.63 installed from the default repos. I am running into a 
> problem that i've seen reported before. There are symbols missing from 
> the freetds install that are in a sybase library which are referenced in 
> the pythong-sybase code base.
> 
> CS_DESCRIBE_OUTPUT
> 
> is one of them. there are others. In digging through the archives of 
> various places, I also saw this kind of thing reported back in 2001 
> against a freetds release. When looking through the includes for both 
> libraries I see that the macros have different values so it probably is 
> not possible to just add them from the sybase version.
> 
> Is there a workaround from the python-sybase side of things or do I need 
> to pursue this via the freetds lists? I do notice that the reported linux 
> builds are all against the sybase version of the libraries. It would be 
> nice to have a viable freetds implementation.
> 
> Dave
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Python-sybase-misc mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-sybase-misc