| Subject: | Fix for perlpath problem |
Here's the requested patch. I'm not exactly sure what the problem was with the original, I could never reproduce it.
This doesn't exactly solve the issue either, it's just a slight step forward in certain cases. The real problem is that (surprisingly, after so many years) there's apparently no way to figure out a path to the currently running perl interpreter. So we're sort of guessing.
-Ken
--- lib/Test/Harness.pm~ Fri Mar 15 10:49:34 2002
+++ lib/Test/Harness.pm Thu Mar 28 20:08:09 2002
@@ -710,10 +710,11 @@
my $s = _set_switches($test);
# XXX This is WAY too core specific!
+ my $perl = -x $^X ? $^X : $Config{perlpath};
my $cmd = ($ENV{'HARNESS_COMPILE_TEST'})
? "./perl -I../lib ../utils/perlcc $test "
. "-r 2>> ./compilelog |"
- : "$Config{perlpath} $s $test|";
+ : "$perl $s $test|";
$cmd = "MCR $cmd" if $^O eq 'VMS';
if( open(PERL, $cmd) ) {