DBI 1.52 was released in August 2006.  Why do you need to use software that
is almost a decade old?

Are you sure that the software you're using will break with the 1.6xx
versions?  Why?  It is relatively unusual for a newer version of DBI to
break older code.  Are you sure it wouldn't be simpler to fix whatever is
broken?

Is the software you're planning to use with DBI 1.52 similarly archaic?


Really and truly, you should be aiming to use a more recent version of DBI.

However, you have three test failures.  One appears to be a bug in the test
code.  The other two appear to be related to 'thread cloning'.  Is your
production system going to be using threads and cloning?  If not, you can
probably use what you've got and built.  It isn't ideal, but then the whole
scenario is not ideal.


On Sat, Dec 26, 2015 at 8:41 AM, Erick Ocrospoma <zipper1...@gmail.com>
wrote:

>
> I'm trying to install manually Perl DBI 1.52 on a el6 server. I'm doing
> this manually because it comes with DBI 1.6x by default, and this version
> is not the needed one.
>
> So, when I do it manually it fails on make test.
>
>
> This what I see it is failing.
>
> [root@el65 DBI-1.52]# make test
> PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e"
> "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
> t/01basics.t ............. ok
> t/02dbidrv.t ............. ok
> t/03handle.t ............. ok
> t/04mods.t ............... ok
> t/05thrclone.t ........... 1/? # Looks like you planned 43 tests but ran
> 44.
> t/05thrclone.t ........... Dubious, test returned 255 (wstat 65280, 0xff00)
> All 43 subtests passed
> t/06attrs.t .............. ok
> t/07kids.t ............... ok
> t/08keeperr.t ............ ok
> t/09trace.t .............. ok
> t/10examp.t .............. 1/263 Can't
> DBI::st=HASH(0x27ba750)->bind_col(1, SCALAR(0x26dd958),...), need a
> reference to a scalar at blib/lib/DBI.pm line 1831.
> # Looks like you planned 263 tests but ran 79.
> # Looks like your test exited with 2 just after 79.
> t/10examp.t .............. Dubious, test returned 2 (wstat 512, 0x200)
> Failed 184/263 subtests
> t/11fetch.t .............. ok
> t/14utf8.t ............... ok
> t/15array.t .............. ok
> t/20meta.t ............... ok
> t/30subclass.t ........... ok
> t/40profile.t ............ ok
> t/41prof_dump.t .......... ok
> t/42prof_data.t .......... ok
> t/43prof_env.t ........... ok
> t/50dbm.t ................ ok
> t/60preparse.t ........... ok
> t/70callbacks.t .......... ok
> t/72childhandles.t ....... ok
> t/80proxy.t .............. skipped: modules required for proxy are
> probably not installed (e.g., RPC/PlClient.pm)
> t/pod.t .................. skipped: Test::Pod 1.00 required for testing POD
> t/zvpp_01basics.t ........ ok
> t/zvpp_02dbidrv.t ........ ok
> t/zvpp_03handle.t ........ ok
> t/zvpp_04mods.t .......... ok
> t/zvpp_05thrclone.t ...... 1/? # Looks like you planned 43 tests but ran
> 44.
> t/zvpp_05thrclone.t ...... Dubious, test returned 255 (wstat 65280, 0xff00)
> All 43 subtests passed
> t/zvpp_06attrs.t ......... ok
> t/zvpp_07kids.t .......... skipped: $h->{Kids} attribute not supported for
> DBI::PurePerl
> t/zvpp_08keeperr.t ....... ok
> t/zvpp_09trace.t ......... ok
> t/zvpp_10examp.t ......... ok
> t/zvpp_11fetch.t ......... ok
> t/zvpp_14utf8.t .......... ok
> t/zvpp_15array.t ......... ok
> t/zvpp_20meta.t .......... ok
> t/zvpp_30subclass.t ...... ok
> t/zvpp_40profile.t ....... skipped: profiling not supported for
> DBI::PurePerl
> t/zvpp_41prof_dump.t ..... skipped: profiling not supported for
> DBI::PurePerl
> t/zvpp_42prof_data.t ..... skipped: profiling not supported for
> DBI::PurePerl
> t/zvpp_43prof_env.t ...... skipped: profiling not supported for
> DBI::PurePerl
> t/zvpp_50dbm.t ........... ok
> t/zvpp_60preparse.t ...... skipped: preparse not supported for
> DBI::PurePerl
> t/zvpp_70callbacks.t ..... skipped: $h->{Callbacks} attribute not
> supported for DBI::PurePerl
> t/zvpp_72childhandles.t .. ok
> t/zvpp_80proxy.t ......... skipped: modules required for proxy are
> probably not installed (e.g., RPC/PlClient.pm)
>
> Test Summary Report
> -------------------
> t/05thrclone.t         (Wstat: 65280 Tests: 44 Failed: 1)
>   Failed test:  44
>   Non-zero exit status: 255
>   Parse errors: Plan (1..43) must be at the beginning or end of the TAP
> output
>                 Bad plan.  You planned 43 tests but ran 44.
> t/10examp.t            (Wstat: 512 Tests: 79 Failed: 0)
>   Non-zero exit status: 2
>   Parse errors: Bad plan.  You planned 263 tests but ran 79.
> t/zvpp_05thrclone.t    (Wstat: 65280 Tests: 44 Failed: 1)
>   Failed test:  44
>   Non-zero exit status: 255
>   Parse errors: Plan (1..43) must be at the beginning or end of the TAP
> output
>                 Bad plan.  You planned 43 tests but ran 44.
> Files=49, Tests=2138,  3 wallclock secs ( 0.41 usr  0.20 sys +  1.70 cusr
>  0.81 csys =  3.12 CPU)
> Result: FAIL
> Failed 3/49 test programs. 2/2138 subtests failed.
> make: *** [test_dynamic] Error 255
>
>
> As far as I can see, this is not good. Or I could ignore it and install it
> with make install ?
>

​I'd go with 'make install' unless you have a concrete reason to think that
the thread clone test failures are going to cause you trouble.​


> I suspect is due to Perl 5.10.1, which comes with el6. On el5, where DBI
> 1.52 can be installed, Perl 5.8.8 is the default version.
>

​Note that neither Perl 5.8.8 or 5.10.1 is exactly optimal.  The last Perl
5.8 was 5.8.9 (though the differences are probably minor), released
December 2008.  The last Perl 5.10 version was 5.10.1, released August
2009.  Both are definitively end of life as far as Perl is concerned (see
http://www.cpan.org/src/README.html, but I recognize the various operating
systems still use old versions that are technically end of life).  You
should be upgrading to, say, Perl 5.22.1 (since that's current).

-- 
Jonathan Leffler <jonathan.leff...@gmail.com>  #include <disclaimer.h>
Guardian of DBD::Informix - v2015.1101 - http://dbi.perl.org
"Blessed are we who can laugh at ourselves, for we shall never cease to be
amused."

Reply via email to