On Thu, Mar 02, 2006 at 03:47:03PM -0600, Dirk Eddelbuettel wrote: Content-Description: message body text
> On 2 March 2006 at 13:18, Steve Langasek wrote:
> | On Thu, Mar 02, 2006 at 10:58:23AM -0600, Dirk Eddelbuettel wrote:
> | > Upstream's changelog doesn't reveal anything either:
> | On the contrary, the first entry is suspicious:
> | > Version: 1.1-5 (2006-01-10, released)
> | > * Added a cast in RODBC.c to counteract a warning Dirk Eddelbuettel
> | > got (and I do not on either Linux or Windows).
> | Casting away warnings is frequently a bug, and an architecture-specific one.
> I have forgotten the details, but I think that this was harmless.
> | So with RODBC the only variable here, I'm still pretty sure it's an RODBC
> | bug.
> I still doubt, but you've proven me wrong often enough :) Anyway, the 1.1.3
> to 1.1.5 diff is attached. I see no smoking gun. RODBC.c is at the end after
> a lot of debian/, configure, and documentation changes that seem irrelevant
> in this context.
@@ -757,7 +758,7 @@
thisHandle->hStmt, sqlstate, &NativeError,
msg, (SQLSMALLINT)sizeof(msg), &MsgLen)
== SQL_SUCCESS) {
- if(strcmp(sqlstate, "O1004") == 0)
+ if(strcmp((char *)sqlstate, "O1004") == 0)
warning(_("character data truncated in column '%s'"),
(char *)thisHandle->ColData[i].ColName);
}
Yeah.. you're right, this is harmless. :)
Ok, the other possibility is that there's a difference in the build
environment between 1.1.3 and 1.1.5 -- which there is: unixodbc bumped from
version 2.2.4 to 2.2.11 between sarge and etch. Johannes, could you try to
rebuild the rodbc package from sarge using unixodbc-dev_2.2.11-9, and see if
that also shows the failure?
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
