New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Win32 MinGW cannot start coretest due to bash-specific ENV prefixing #1965
Comments
From @Util$ git show | head -1 In build/Makefile.in, the target "coretest" sets PARROT as an ENV The method used to set PARROT is unix-specific, and fails under Win32. The spectest target is not dependent on coretest, Solution: The attached patch is ready to push into the Rakudo master repo. After release, we should consider making spectest_smolder depend on |
From @Utilcoretest_env_bugfix.patchdiff --git a/build/Makefile.in b/build/Makefile.in
index 7b88140..689d245 100644
--- a/build/Makefile.in
+++ b/build/Makefile.in
@@ -408,7 +408,7 @@ test : coretest
fulltest: coretest stresstest
coretest: Test.pir $(PERL6_EXE)
- PARROT=$(PARROT) $(PERL) t/harness t/00-parrot t/01-sanity t/02-embed
+ $(PERL) t/harness t/00-parrot t/01-sanity t/02-embed
# Run the spectests that we know work.
spectest_regression: spectest
diff --git a/t/02-embed/01-load.t b/t/02-embed/01-load.t
index 709a5f3..c4ff03a 100644
--- a/t/02-embed/01-load.t
+++ b/t/02-embed/01-load.t
@@ -1,3 +1,5 @@
use v6;
-my $parrot = %*ENV{'PARROT'};
+my $bindir = $*VM<config><bindir> or die 'No bindir found';
+my $exe = $*VM<config><exe> // '';
+my $parrot = "$bindir/parrot$exe";
run("$parrot t/02-embed/01-load.pir");
|
From @Util-- |
@coke - Status changed from 'new' to 'open' |
From @cokeOn Thu Jul 22 13:19:22 2010, util wrote:
util - Sorry about the huge delay in replying here, but this patch doesn't apply cleanly anymore. If you're still having trouble running rakudo tests on your setup, please open a new ticket. Regards. -- |
@coke - Status changed from 'open' to 'rejected' |
Migrated from rt.perl.org#76680 (status was 'rejected')
Searchable as RT76680$
The text was updated successfully, but these errors were encountered: