[perl5-dbi/dbi] bc7801: Fix compile warnings in Driver.xst

paths: M Driver.xst M Perl.xs Log Message: --- Fix compile warnings in Driver.xst Perl.c: In function ‘XS_DBD__Perl__dr_data_sources’: Perl.c:276:7: warning: variable ‘attr’ set but not used [-Wunused-but-set-variable] SV * attr; ^~~~ Perl.c: In fu

warnings since last DBI release

In file included from ODBC.c:70: /usr/local/lib/perl/5.10.1/auto/DBI/Driver_xst.h: In function ‘dbdxst_bind_params’: /usr/local/lib/perl/5.10.1/auto/DBI/Driver_xst.h:72: warning: passing argument 2 of ‘imp_sth-com.std.dbistate-set_err_char’ from incompatible pointer type

Re: warnings since last DBI release

/usr/include dbdimp.c It is 2 added calls to DBIh_SET_ERR_CHAR in Driver_xst.h. Warnings (on HP-UX 11.31/5.14.2-64all-ld) *in* last release: DBI.xs, line 1469: warning #4232-D: conversion from XPVHV * to a more strictly aligned type XPVMG * may cause misaligned access

Re: warnings since last DBI release

On Fri, 03 Feb 2012 15:42:40 +, Martin J. Evans martin.ev...@easysoft.com wrote: On 03/02/12 15:16, Tim Bunce wrote: On Fri, Feb 03, 2012 at 11:22:19AM +0100, H.Merijn Brand wrote: Warnings (on HP-UX 11.31/5.14.2-64all-ld) *in* last release: DBI.xs, line 1469: warning #4232-D

Warnings

Hey All, Just installed 1.614 on three of my boxes. Looks good, and thanks for getting it out! I did notice some warnings, though: /usr/local/bin/perl /usr/local/lib/perl5/5.12.2/ExtUtils/xsubpp -typemap /usr/local/lib/perl5/5.12.2/ExtUtils/typemap -typemap typemap DBI.xs DBI.xsc mv

Re: Warnings

On 17/09/2010 19:51, David E. Wheeler wrote: Hey All, Just installed 1.614 on three of my boxes. Looks good, and thanks for getting it out! I did notice some warnings, though: /usr/local/bin/perl /usr/local/lib/perl5/5.12.2/ExtUtils/xsubpp -typemap /usr/local/lib/perl5/5.12.2/ExtUtils

Re: Warnings

On Fri, Sep 17, 2010 at 09:13:20PM +0100, Martin J. Evans wrote: DBI.xs:4965: warning: value computed is not used New DBIx::Connector now on its way to CPAN, too. Thanks. They are all hv_store calls and hv_store returns a value. I think they are all harmless and the only way to make them

Re: DBD::Pg emits some warnings despite PrintError = 0

Lyle wrote: Hi, So far I've seen: NOTICE: CREATE TABLE / UNIQUE will create implicit index FOO_BAR for table FOO Lyle Did you look at PrintWarn. Martin -- Martin J. Evans Easysoft Limited http://www.easysoft.com

Re: DBD::Pg emits some warnings despite PrintError = 0

On 22/07/2010 07:40, Martin J. Evans wrote: Lyle wrote: Hi, So far I've seen: NOTICE: CREATE TABLE / UNIQUE will create implicit index FOO_BAR for table FOO Lyle Did you look at PrintWarn. Opps sorry, serves me right for sending email right before I go to sleep :/

DBD::Pg emits some warnings despite PrintError = 0

Hi, So far I've seen: NOTICE: CREATE TABLE / UNIQUE will create implicit index FOO_BAR for table FOO Lyle

Re: DBD::DB2: handling warnings

On Tue, Dec 30, 2008 at 12:37:05PM -0500, Hildo Biersma wrote: The DBD::DB2 driver does not handle warnings in a manner consistent with other DBD drivers. Specifically, if the trace level is lower than 3, warnings are ignored; if the trace level is 3 or above, warnings are treated like

DBD::DB2: handling warnings

The DBD::DB2 driver does not handle warnings in a manner consistent with other DBD drivers. Specifically, if the trace level is lower than 3, warnings are ignored; if the trace level is 3 or above, warnings are treated like errors. The driver also directly manipulates the DBI internals

Re: Warnings during compilation of dbd-mysql on Mac OS X (for Fink distro)

* dbd_db_FETCH_attrib(dbh, imp_dbh_t* imp_dbh, SV* keysv) { ... Indeed, dbh is never used. not sure if I have to adhere to passing a dbh handle as first arg or can do some sort of __unused__ in the code to stifle these warnings. I just don't want to rip too much out, so I'm methodically going

Re: Warnings during compilation of dbd-mysql on Mac OS X (for Fink distro)

the maintainer of the Fink packages for dbd-mysql on Mac OS X: http://pdb.finkproject.org/pdb/package.php/dbd-mysql-pm586 I am trying to update the packages to version 4.005. But I get a lot of warnings during the compilation (see output below). Are these harmless? Can I ignore them? Am I doing

Re: Warnings during compilation of dbd-mysql on Mac OS X (for Fink distro)

for your efforts! Christian. Christian Schaffner wrote: Hi Patrick I am the maintainer of the Fink packages for dbd-mysql on Mac OS X: http://pdb.finkproject.org/pdb/package.php/dbd-mysql-pm586 I am trying to update the packages to version 4.005. But I get a lot of warnings during

Re: DBD::Oracle: 'no prototype' warnings (Borland)

. Thanks, applied! Finally, a small patch to Makefile.PL that switches bcc to picky mode (force C++). Compiles like a charm: zero errors / zero warnings. Steffen --- Makefile.PL.origMon Sep 13 14:40:20 2004 +++ Makefile.PL Sat Oct 02 22:55:04 2004 @@ -62,6 +62,7 @@ $opts{CAPI} = 'TRUE

Re: DBD::Oracle: 'no prototype' warnings (Borland)

and that requires ANSI C. O.k., attached are the KR = ANSI patches for dbdimp.c and oci8.c. Thanks, applied! Finally, a small patch to Makefile.PL that switches bcc to picky mode (force C++). Compiles like a charm: zero errors / zero warnings. Thanks, applied! Tim. Steffen --- Makefile.PL.orig

Re: DBD::Oracle: 'no prototype' warnings (Borland)

Tim Bunce wrote: I can live with assuming support for ANSI C style prototypes since we already effectively require perl 5.6 and that requires ANSI C. O.k., attached are the KR = ANSI patches for dbdimp.c and oci8.c. Steffen --- dbdimp.orig Thu Sep 30 14:26:04 2004 +++ dbdimp.cThu Sep 30

Re: DBD::Oracle: 'no prototype' warnings (Borland)

On Fri, Oct 01, 2004 at 01:46:45PM +0200, Steffen Goeldner wrote: Tim Bunce wrote: I can live with assuming support for ANSI C style prototypes since we already effectively require perl 5.6 and that requires ANSI C. O.k., attached are the KR = ANSI patches for dbdimp.c and oci8.c. Thanks,

Re: DBD::Oracle: 'no prototype' warnings (Borland)

On Thu, Sep 30, 2004 at 10:29:25AM +0200, Steffen Goeldner wrote: Tim Bunce wrote: On Wed, Sep 22, 2004 at 03:52:09PM +0200, Steffen Goeldner wrote: Compiling DBD::Oracle with Borland C++ 5.5, I have a bunch of warnings: [...] 1. ignore the warnings :-( 2. suppress the warnings (-w

Re: DBD::Oracle: 'no prototype' warnings (Borland)

Tim Bunce wrote: On Wed, Sep 22, 2004 at 03:52:09PM +0200, Steffen Goeldner wrote: Compiling DBD::Oracle with Borland C++ 5.5, I have a bunch of warnings: [...] 1. ignore the warnings :-( 2. suppress the warnings (-w-8065) 3. Force __STDC__=1 4. Force C++ compile (-P): 5. Remove the #if/#else

DBD::Oracle: 'no prototype' warnings (Borland)

Compiling DBD::Oracle with Borland C++ 5.5, I have a bunch of warnings: Warning W8065 ...: Call to function 'OCI...' with no prototype in function because oci.h includes the KR headers: #if defined(__STDC__) || defined(__cplusplus) #include ociapr.h #include ociap.h #else #include

New DBI mechanisms for handling SUCCESS_WITH_INFO and warnings

and for information. Both values are false and so don't trigger RaiseError etc. Warnings (err=0) are automatically printed if PrintError is set. Thanks to Steffen Goeldner for the original idea. Added $h-{HandleSetError} = sub { ... } to be called at the point that an error, warn

Re: DBI 1.31 Warnings

Thanks. There're harmless but I've fixed them for the next release. Tim. On Sat, Nov 30, 2002 at 11:33:38AM -0800, David Wheeler wrote: I got some warnings while compiling DBI 1.31 on Mac OS X 10.2.2. Here's the version of gcc I'm using: mercury% cc -v Reading specs from /usr/libexec/gcc

DBI 1.31 Warnings

I got some warnings while compiling DBI 1.31 on Mac OS X 10.2.2. Here's the version of gcc I'm using: mercury% cc -v Reading specs from /usr/libexec/gcc/darwin/ppc/3.1/specs Thread model: posix Apple Computer, Inc. GCC version 1161, based on gcc version 3.1 20020420 (prerelease