mx.ODBC/Cygwin/Python 2.1.1

Steve Holden sholden at holdenweb.com
Wed Oct 3 12:25:34 EDT 2001


Has anyone built the mxCommercial extensions for Cygwin? I'm having many
problems which look so fundamental I'm hoping they have a really simple fix.
This is where they begin:

running build_ext
building 'mx.ODBC.iODBC.mxODBC' extension
gcc -g -O2 -Wall -Wstrict-prototypes -DUSE_DL_IMPORT -DiODBC -Imx/ODBC/iODBC
 -I/usr/local/include -I/usr/include/python2.1 -c mx/ODBC/iODBC/mxODBC.c -o
build/temp.cygwin-1.3.3-i686-2.1/mxODBC.o
In file included from /usr/include/w32api/sql.h:9,
                 from mx/ODBC/iODBC/mxODBC.h:239,
                 from mx/ODBC/iODBC/mxODBC.c:33:
/usr/include/w32api/sqltypes.h:13: parse error before `UDWORD'
/usr/include/w32api/sqltypes.h:13: warning: data definition has no type or
storage class
/usr/include/w32api/sqltypes.h:14: parse error before `UWORD'
/usr/include/w32api/sqltypes.h:14: warning: data definition has no type or
storage class
/usr/include/w32api/sqltypes.h:20: parse error before `PTR'
/usr/include/w32api/sqltypes.h:20: warning: data definition has no type or
storage class

Things get rapidly worse from there, with serious errors reported in other
include files, eventually leading to errors compiling
mx/ODBC/iODBC/mxODBC.c.

Anyone know the answer? I've mailed Marc-Andre Lemburg directly, but he may
well be too busy to help.

regards
 Steve
--
http://www.holdenweb.com/







More information about the Python-list mailing list