Re: Errors compiling psqlodbc - Mailing list pgsql-odbc
From | Rich Silva |
---|---|
Subject | Re: Errors compiling psqlodbc |
Date | |
Msg-id | 20041017195749.AEM6960.lakecmmtao02.coxmail.com@CALICOBASS Whole thread Raw |
In response to | Re: Errors compiling psqlodbc ("Dave Page" <dpage@vale-housing.co.uk>) |
Responses |
Re: Errors compiling psqlodbc
|
List | pgsql-odbc |
Thanx, I also received a reply from Peter on some of this... Good to know the 08.00.0002 branch is "stable"... We'll give that a try... Rich > -----Original Message----- > From: Dave Page [mailto:dpage@vale-housing.co.uk] > Sent: Sunday, October 17, 2004 10:57 AM > To: Rich Silva; pgsql-odbc@postgresql.org > Subject: RE: [ODBC] Errors compiling psqlodbc > > Apologies for top posting (dodgy webmail)... > > With 07.03.0200, 2.5 *was* the correct default ODBC version. That has been > removed from the current code for some time now though, so fixes or bugs > related to the ODBC version are now pretty much irrelevant unless they are > also present in the current code. > > The 08.00.0002 snapshot is pretty stable judging by the lack of bugs > reports we have seen about it - please try that version. > > Regards, Dave. > > > > -----Original Message----- > From: pgsql-odbc-owner@postgresql.org on behalf of Rich Silva > Sent: Sat 10/16/2004 11:58 PM > To: pgsql-odbc@postgresql.org > Subject: [ODBC] Errors compiling psqlodbc > > > > > > Hmmm, I was building the latest (07.03.0200) sources for a Linux system > and > I found first one then another issue. > > > > First issue (and already submitted as a bug): The default ODBCVER is not > 0x0300, but 0x0250. Configure does not set ODBCVER unless the -with- > odbcver > option is used. In psqlodbc.h, if ODBCVER is not set it defaults to > 0x0250. > I'm now using the configure line: > > > > ./configure --with-unixodbc --prefix=/usr --sysconfdir=/etc > --with-odbcver=0x0300 > > > > Second issue (and still diagnosing), once I've configured with that define > the project will not compile, generating the following errors: > > convert.c: In function `copy_and_convert_field': > > convert.c:1194: incompatible types in assignment > > convert.c:1196: incompatible types in assignment > > convert.c:1202: incompatible types in assignment > > convert.c:1204: incompatible types in assignment > > (example line: *((SQLBIGINT *) rgbValueBindRow) = ATOI64(neut_str);) > > > > odbcapi.c: In function `SQLFetch': > > odbcapi.c:349: warning: initialization from incompatible pointer type > > (line: SQLINTEGER *pcRow = irdopts->rowsFetched;) > > > > odbcapi30.c: In function `SQLFetchScroll': > > odbcapi30.c:204: warning: initialization from incompatible pointer type > > (line: SQLINTEGER *pcRow = irdopts->rowsFetched, bkmarkoff = 0;) > > > > pgapi30.c: In function `IRDSetField': > > pgapi30.c:755: warning: assignment from incompatible pointer type > > (example: opts->rowsFetched = (SQLUINTEGER *) Value;) > > pgapi30.c: In function `IPDSetField': > > pgapi30.c:811: warning: assignment from incompatible pointer type > > pgapi30.c: In function `PGAPI_GetStmtAttr': > > pgapi30.c:1424: warning: assignment from incompatible pointer type > > pgapi30.c:1440: warning: assignment from incompatible pointer type > > pgapi30.c:1448: warning: assignment from incompatible pointer type > > pgapi30.c:1460: warning: assignment from incompatible pointer type > > pgapi30.c: In function `PGAPI_SetStmtAttr': > > pgapi30.c:1685: warning: assignment from incompatible pointer type > > pgapi30.c:1697: warning: assignment from incompatible pointer type > > pgapi30.c:1703: warning: assignment from incompatible pointer type > > pgapi30.c:1712: warning: assignment from incompatible pointer type > > > > Now, I'm not yet claiming to be a programmer, so I'm hoping that someone > has > tackled these before. > > > > Thanx for the help! > > Rich Silva > >
pgsql-odbc by date: