Andreas J. Koenig wrote:
Now it looks more like a MakeMaker problem.
Try with the attached patch (which steals the logic from perlvar to
produce a more accurate representation of the currently running Perl
than does $^X).
John
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5748
=== t/002_config.t
==================================================================
--- t/002_config.t (revision 570)
+++ t/002_config.t (local)
@@ -1,3 +1,9 @@
+use Config;
+my $secure_perl_path = $Config{perlpath};
+if ($^O ne 'VMS') {
+ $secure_perl_path.= $Config{_exe}
+ unless $secure_perl_path =~ m/$Config{_exe}$/i;
+}
require "t/coretests.pm";
reset_all_tests();
@@ -2,2 +8,2 @@
initialize_results("results.yml");
-run_tests("perl t/002_config");
+run_tests("$secure_perl_path t/002_config");
=== t/003_config.t
==================================================================
--- t/003_config.t (revision 570)
+++ t/003_config.t (local)
@@ -1,3 +1,9 @@
+use Config;
+my $secure_perl_path = $Config{perlpath};
+if ($^O ne 'VMS') {
+ $secure_perl_path.= $Config{_exe}
+ unless $secure_perl_path =~ m/$Config{_exe}$/i;
+}
require "t/coretests.pm";
reset_all_tests();
@@ -2,2 +8,2 @@
initialize_results("results2.yml");
-run_tests("perl t/003_config");
+run_tests("$secure_perl_path t/003_config");
