Interesting excuse to go delving through the CPAN.pm source code. I also had alterior motives. I wanted to see how to change the order of which facility is used to fetch modules. I have CPAN 1.63 and ActivePerl build 5.6.1 633 on Windows 2000
My conclusion is that you may have differences in the Cygwin install on the machines. That is, the error comes from tar.exe or something it depends on.
Here is why I think that:
As far as I know system() on win32 has no problems with people using either forward slashes or back slashes in paths5746 $system = "$CPAN::Config->{tar} xvf $file"; 5747 $CPAN::Frontend->myprint(qq{Using Tar:$system:\n}); 5748 if (system($system)==0) { 5749 $CPAN::Frontend->myprint(qq{Untarred $file successfull +y\n}); 5750 } else { 5751 $CPAN::Frontend->mydie(qq{Couldn\'t untar $file\n}); 5752 }
/usr/bin/tar: F\:\\.cpan\\sources\\authors\\id\\M\\MS\\MSCHWERN\\Carp- +Assert-0.17.tar: Cannot open: I/O error
tar.exe is saying cannot open due to I/O error
Using Tar:c:\cygwin\bin\tar.exe xvf \.cpan\sources\authors\id\M\MS\MSC +HWERN\Carp -Assert-0.17.tar: Carp-Assert-0.17/ Carp-Assert-0.17/t/ Carp-Assert-0.17/t/30no_disabled.t /usr/bin/tar: Skipping to next header /usr/bin/tar: Error exit delayed from previous errors Couldn't untar \.cpan\sources\authors\id\M\MS\MSCHWERN\Carp-Assert-0.1 +7.tar cpan>
After searching around I found an alterative tar.exe which I use now. It works OK except when you specify the full path to it. When you do you get an error locating cygwin.dll. <sigh>
So basically tar.exe on Win32 with Cygwin sucks and I still wish I could throw Windows out and use linux (even better: Solaris on a Blade so I can finish my Sun Admin certification. :-)
--blm--In reply to Re: CPAN weirdness on Win32
by blm
in thread CPAN weirdness on Win32
by demerphq
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |