Peter Prymmer wrote:
Peter Prymmer <[EMAIL PROTECTED]> wrote on 03/07/2006 11:42:38 PM:
Sorry but I have made no progress on this problem. I am concerned.
I now suspect that there is a VMS specific bug in File::Path::mkpath.
If I add a diagnostic print statement to that module like so:
$ gdiff -u [.lib.file]path.pm [.lib.file]path.pm;1
--- [.lib.file]path.pm Wed Mar 8 16:25:15 2006
+++ [.lib.file]path.pm;1 Wed Sep 7 10:59:46 2005
@@ -168,7 +168,6 @@
next if -d $path;
my $parent = File::Basename::dirname($path);
unless (-d $parent or $path eq $parent) {
-print "\$parent = >$parent<, \$path = >$path<\n";
push(@created,mkpath($parent, $verbose, $mode));
}
print "mkdir $path\n" if $verbose;
Then when I run "mmk install" I see:
$parent = >/perl_root<, $path = >/perl_root/000000<
Clearly something is wrong, the '/000000' should not be present because
it will not be understood by the C runtime. It might help if you can
find out what is adding it.
I am pretty sure that I exorcised all the code that was incorrectly
adding '/000000' from both vms.c and configure.com.
-John
[EMAIL PROTECTED]
Personal Opinion Only
