[Asterisk-Users] CVS compile issue on res_odbc.o

[David Shirley]

Hi,

I've been having some echo problems on SIP calls with 1.0.7, so I 
wanted to take the latest CVS to see if it has the same issue. However, 
I cannot get it to compile and having searched these lists and Googled 
elsewhere, I can't find any references to a similar problem. This is 
what I get:

make[1]: Leaving directory `/usr/src/asterisk/stdtime'
if [ -d CVS ] && [ ! -f .version ]; then echo 
CVS-HEAD-04/08/05-11:58:53 > .version; fi
for x in res channels pbx apps codecs formats agi cdr utils stdtime; do 
make -C $x || exit 1 ; done
make[1]: Entering directory `/usr/src/asterisk/res'
gcc -pipe  -Wall -Wstrict-prototypes -Wmissing-prototypes 
-Wmissing-declarations -g  -Iinclude -I../include -D_REENTRANT 
-D_GNU_SOURCE  -O6 -march=i686  -DZAPTEL_OPTIMIZATIONS  
-DASTERISK_VERSION=\"CVS-HEAD-04/08/05-11:58:53\" 
-DASTERISK_VERSION_NUM=999999 -DINSTALL_PREFIX=\"\" 
-DASTETCDIR=\"/etc/asterisk\" -DASTLIBDIR=\"/usr/lib/asterisk\" 
-DASTVARLIBDIR=\"/var/lib/asterisk\" -DASTVARRUNDIR=\"/var/run\" 
-DASTSPOOLDIR=\"/var/spool/asterisk\" -DASTLOGDIR=\"/var/log/asterisk\" 
-DASTCONFPATH=\"/etc/asterisk/asterisk.conf\" 
-DASTMODDIR=\"/usr/lib/asterisk/modules\" 
-DASTAGIDIR=\"/var/lib/asterisk/agi-bin\"     -DBUSYDETECT_MARTIN     
-fomit-frame-pointer    -DZAPATA_MOH  -DOPENSSL_NO_KRB5 -fPIC   -c -o 
res_odbc.o res_odbc.c
res_odbc.c: In function `odbc_sanity_check':
res_odbc.c:126: `SQLLEN' undeclared (first use in this function)
res_odbc.c:126: (Each undeclared identifier is reported only once
res_odbc.c:126: for each function it appears in.)
res_odbc.c:126: parse error before `rowcount'
res_odbc.c:142: `rowcount' undeclared (first use in this function)
res_odbc.c: In function `odbc_obj_connect':
res_odbc.c:476: warning: passing arg 5 of `SQLGetDiagRec' from 
incompatible pointer type
make[1]: *** [res_odbc.o] Error 1
make[1]: Leaving directory `/usr/src/asterisk/res'
make: *** [subdirs] Error 1

I'm running this on a RedHat Enterprise Linux ES 2.1 system, which is 
fully patched. Does anyone have any ideas what could be causing this?

Thanks in advance,

David Shirley