Michal Jurosz <[EMAIL PROTECTED]> wrote:
> Failed Test Status Wstat Total Fail Failed List of Failed
[ 50 failing ]
> imcc/t/imcpasm/opt1.# Failed test (imcc/t/imcpasm/opt1.t at line 626)
> # got: '_main:
> # set N0, 1.6e+022
> # end
> # '
> # expected: '_main:
> # set N0, 1.6e+22
The test could include C< 0? >.
> --- imcc/t/syn/file.t, line 363
> { local $/; $err_msg = <FOO>; }
> + $err_msg =~ s/\r//g;
Could you please provide one patch for items like above, thanks.
> t/dynclass/pybuiltin.# Failed test (t/dynclass/pybuiltin.t at line 22)
dynclasses/* are currently failing on windows due to missing exported
symbols.
> t/native_pbc/integer.# Failed test (t/native_pbc/integer.t at line 51)
> # got: 'Parrot VM: Can't locate
> c:/usr/parrot-t/t/native_pbc/integer_1.pbc, code 2.
> # main: Packfile loading failed
Strange. Can you run that through a debugger?
> t/op/spawnw.........# Failed test (t/op/spawnw.t at line 57)
> # got: 'return code: 0
> # '
> # expected: 'return code: 123
The win32:Parrot_Run_OS_Command could be the culprit (see
src/platform.c, which is constructed from various platform files
mentioned there as comments)
> not ok 19 - constructor - diamond parents # TODO wrong init order?
> # Failed (TODO) test (t/pmc/object-meths.t at line 519)
That's an TODO test, but already fixed in CVS.
> # Failed (TODO) test (t/pmc/objects.t at line 1660)
TODO's are supposed to fail.
> # --- t/pmc/sys ---
> t/pmc/sys...........# Failed test (t/pmc/sys.t at line 26)
> # got: '. Not found ...
> --- config_lib.pasm
> - set P0["slash"], "/"
> + set P0["slash"], "\\"
> $ parrot config_lib.pasm
No. This file is generated and should contain the current setting of
$Pconfig{slash} - see also lib/Parrot/Config.pm.
> $ parrot.exe t/pmc/sys_1.imc
> Hello, World!
> 0
> So seems like Parrot_run_slash != MinGW_build_slash. Because I still
> need Configure::Data->set( slash => '/' ); inside
> config\init\mswin32.pl to properly build.
What is the difference between these two slashes - looks strange.
> # --- Some other ideas: ---
> $ perl -e "print $^O"
> msys
> --- config\init\hints.pl
> sub runstep {
> + my $O = lc($^O);
> + $O = 'mswin32' if $O =~ /^(msys|mingw)/;
> - my $hints = "config/init/hints/" . lc($^O) . ".pl";
> + my $hints = "config/init/hints/" . $O . ".pl";
This would make MinGW in all aspects identical to a native window build,
wouldn't it? Seems dangerous.
> S pozdravem Michal Jurosz
Thanks for the detailed report,
It would be great if folks with windows installed could have a look at
these issues.
leo
