On 10/05/2010 17:44, Tim Bunce wrote:
On Sun, Mar 28, 2010 at 11:40:35PM +0200,
rosenfield.alb...@gmail.com wrote:
> In practice this results in circa 70% of smoke testers running the
> module with DBI installed.
>
> The remaining 30% however, fails with this error:
> ================================= # Failed test 'use DBI;' #
> at t/00-load.t line 4. # Tried to use 'DBI'. # Error:
> Can't locate DBI.pm in @INC (@INC contains: [...snip...]) at (eval
> 4) line 2. # BEGIN failed--compilation aborted at (eval 4) line 2.
> =================================
>
> I could easily change the "use DBI" line into a conditional
> "require DBI::PurePerl" during BEGIN, but this does not fix the
> root of the problem, namely that the PurePerl version of DBI never
> gets installed.
We don't know the *root* of the problem. The error you quote above
just a symptom of an earlier problem.
Where do you get the 70%/30% ratio from?
I don't know as cpanstats db shows for the last 2 versions:
state, version, count(*)
'fail', '1.609', 44
'na', '1.609', 16
'na', '1.611', 1
'pass', '1.609', 1153
'pass', '1.611', 101
'unknown', '1.609', 11
'unknown', '1.611', 1
4% (rounded up) of failures for fails/passes in 1.609 discounting nas.
The na status are all perls too old (not at least 5.8.1).
Of the fails in 1.609 most are test failures (after compilation) and for
problems Tim has addressed in 1.611.
Of all the failures in 1.609 (44 of them) I got fed up of checking them
after doing over half of them and finding no lack of compiler problems.
In 1.611 the one compiler error is:
*** You're using Microsoft Visual C++ compiler or similar but
the LIB and INCLUDE environment variables are not both set.
You need to run the VCVARS32.BAT batch file that was supplied
with the compiler before you can use it.
A copy of vcvars32.bat can typically be found in the following
directories under your Visual Studio install directory:
Visual C++ 6.0: vc98\bin
Visual Studio .NET: vc7\bin
Find it, run it, then retry this.
If you think this error is not correct then just set the LIB and
INCLUDE environment variables to some value to disable the check.
and DBD::ODBC gets the same error from this particular smoker although
on a different smoking platform.
For DBI it is Win32 with MS VisC 12 and for DBD::ODBC it is Win32 with gcc.
It is hardly surprising DBI and DBD::ODBC produce the same error as I
think the test is in DBI but I've always been confused by the error when
gcc is being used.
I'd like to see details of the specific underlying problems that
cause build failures with the current release. Ideally with some
indication of which are the most frequent.
Tim.
There used to be an http://analysis.cpantesters.org/ (or something like
that) but the link from the cpan testers
wiki does not work now. I got the data from the cpantesters database
but it does not seem to contain the
actual failure report. If someone knows where the report info is I may
be prepared to dig into this a
little deeper but I don't as yet see any evidence that 30% of build
failures are down to lack of a
compiler.
Martin
