develooper Front page | perl.perl5.porters | Postings from August 2009

Re: Building from ext/ doesn't like VMS debug builds (Re: Smoke [5.11.0] blead-1964-g2adbc9b FAIL(F) MSWin32 Win2000 SP4 (x86/1 cpu))

Thread Previous | Thread Next
From:
Nicholas Clark
Date:
August 28, 2009 23:39
Subject:
Re: Building from ext/ doesn't like VMS debug builds (Re: Smoke [5.11.0] blead-1964-g2adbc9b FAIL(F) MSWin32 Win2000 SP4 (x86/1 cpu))
Message ID:
20090829063920.GY60303@plum.flirble.org
There's a bit of context, and then it goes BOOM!

On Fri, Aug 28, 2009 at 08:20:34PM +0100, Nicholas Clark wrote:
> On Fri, Aug 28, 2009 at 10:14:50AM -0500, Craig A. Berry wrote:
> 
> > What we have instead of perl.exe in the top-level directory is
> > dbgperl.exe, which invokes the debugger when you run it, and
> > ndbgperl.exe, which doesn't.  The latter is copied down to t/perl.exe
> > by vms/test.com.  I guess we could copy it two places and make sure
> > there is a perl.exe at the top level, but it seems simpler to use the
> > one that's already in t/.  The following works for me, is there any
> > reason not to do it this way?
> > 
> > --- t/TEST;-0   2009-08-27 18:48:31 -0500
> > +++ t/TEST      2009-08-28 09:55:35 -0500
> > @@ -197,7 +197,7 @@ sub _run_test {
> >             $ext_dir = $1;
> >             $return_dir = '../../t';
> >             $lib = '../../lib';
> > -           $perl = '../../perl';
> > +           $perl = '../../t/perl';
> >             $testswitch = "-I$return_dir -MTestInit=U2T,A";
> >             if ($temp_no_core{$ext_dir}) {
> >                 $testswitch = $testswitch . ',NC';
> > [end]
> 
> I don't see why it won't work, so I've committed it as 1d8d82d3d8b73345e6276774


On Fri, Aug 28, 2009 at 09:27:35PM -0400, George Greer wrote:

> Well this whole thing was sorted out before I got home from work.  What 

Except then, I committed the above innocuous change, and both your and
Steve's smokers went boom:

On Sat, Aug 29, 2009 at 04:21:00AM +0100, Steve Hay wrote:
> Automated smoke report for 5.11.0 patch a2c4b2d6db383103b96e4733616b17d0a3bb0bd9 blead-1969-ga2c4b2d

> Failures: (common-args) -DCCTYPE=MSVC90 -DINST_TOP=$(INST_DRV)\Smoke\doesntexist
> [default] -Duselargefiles
> [default] -DDEBUGGING -Duselargefiles
> [default] -Duselargefiles -Dusemymalloc
> [default] -DDEBUGGING -Duselargefiles -Dusemymalloc
> ../t/op/reg_60508.t.........................................FAILED
> ../lib/maintainers.t........................................FAILED
>     52, 76, 687, 712, 716, 1085, 1127, 1205
>     1365, 1414, 1499, 1625, 2287, 2330, 2495
>     2554, 2557, 2563, 3251-3252, 3281
> ../ext/B/t/concise.t........................................FAILED
>     2-5, 148-157
> ../ext/B/t/lint.t...........................................FAILED
>     1-29
> ../ext/B/t/o.t..............................................FAILED
>     2-5, 7-9
> ../ext/B/t/optree_check.t...................................FAILED
>     11-13
> ../ext/B/t/optree_concise.t.................................FAILED
>     12-14, 16
> ../ext/B/t/optree_constants.t...............................FAILED
>     27-28
> ../ext/B/t/optree_misc.t....................................FAILED
>     2
> ../ext/B/t/optree_samples.t.................................FAILED
>     11, 20
> ../ext/B/t/optree_sort.t....................................FAILED
>     3, 5, 7, 9
> ../ext/B/t/optree_specials.t................................FAILED
>     2-8
> ../ext/B/t/optree_varinit.t.................................FAILED
>     6-8, 13-15, 19-22
> ../ext/B/t/showlex.t........................................FAILED
>     2-3, 9-10
> ../ext/Devel-DProf/t/DProf.t................................FAILED
>     Bad plan.  You planned 20 tests but ran 0.
> ../ext/Devel-PPPort/t/ppphtest.t............................FAILED
>     2-10, 12-15, 18-23, 27, 29-30, 32-40, 42-45
>     47-50, 55, 57-61, 63-64, 66-68, 70-71, 73-75
>     80-81, 83-85, 87, 89-94, 96, 98, 100-113
>     115-129, 131, 134, 136-138, 142-144, 147
>     149-158, 160-162, 164-182, 184-189, 191-209
>     211-214, 216-223, 225-226, 228-230, 232-234
> ../ext/IO-Compress/t/010examples-bzip2.t....................FAILED
>     2-4, 6-8, 10-12, 14-15, 17-19
> ../ext/IO-Compress/t/010examples-zlib.t.....................FAILED
>     2-4, 6-8, 10-12, 14-15, 17-19
> ../ext/IO-Compress/t/cz-05examples.t........................FAILED
>     2-4, 6-8, 10-12, 14-15, 17-19, 21-22, 24-26
> ../ext/Test-Harness/t/perl5lib.t............................FAILED
>     1
> ../ext/Test-Harness/t/process.t.............................FAILED
>     1-27
> ../ext/re/t/lexical_debug.t.................................FAILED
>     1, 3, 5, 7-10
> ../ext/re/t/regop.t.........................................FAILED
>     1, 3-19
>     Bad plan.  You planned 54 tests but ran 19.
> ../lib/strict.t.............................................FAILED
>     77

I think that the connection is that all the failures spawn a new perl
But I'm not sure why they don't like spawning ../../t/perl when ../../perl
worked just fine. Something interpolating, where "\." is \ . but "\t" is
a tab character? But what has that sort of interpolation rule?

Doesn't everything in Perl that interpolates "\t" to a tab also interpolate
"\." to a dot?

Nicholas Clark

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About