Today i had the weirdest thing happen with CPAN. Basically I have two machines that are for all intents and purposes of this node identical. They both have VS DotNet, they both have the latest and same versions of the Cygwin tools. Etc. But for some reason one of them was choking:
(The reason i did a force install with that module was that I know the module is pure perl, and that i had installed it fine previously.)cpan> force install Carp::Assert Running install for module Carp::Assert Running make for M/MS/MSCHWERN/Carp-Assert-0.17.tar.gz Checksum for F:\.cpan\sources\authors\id\M\MS\MSCHWERN\Carp-Assert-0.1 +7.tar.gz ok 'F:' is not recognized as an internal or external command, operable program or batch file. Uncompressed F:\.cpan\sources\authors\id\M\MS\MSCHWERN\Carp-Assert-0.1 +7.tar.gz successfully Using Tar:F:/Cygwin/bin/tar.EXE xvf F:\.cpan\sources\authors\id\M\MS\M +SCHWERN\Carp-Assert-0.17.tar: F: Unknown Host /usr/bin/tar: F\:\\.cpan\\sources\\authors\\id\\M\\MS\\MSCHWERN\\Carp- +Assert-0.17.tar: Cannot open: I/O error /usr/bin/tar: Error is not recoverable: exiting now Couldn't untar F:\.cpan\sources\authors\id\M\MS\MSCHWERN\Carp-Assert-0 +.17.tar
Yet when i did the exact same thing on the second machine it worked just fine.
So after checking everything I could for differences, I realized that the only thing I could see was that in the CPAN/Config.pm the paths were forward slashed on the error box and backslashed on the proper box. Ie:
And when I changed the unix style paths to Win32 style paths everything magically started working.#Error box tar F:/Cygwin/bin/tar.EXE #Ok box tar F:\Cygwin\bin\tar.EXE
I have no idea what the cause of this is, cygwin or CPAN itself. I could see it being either really. But if CPAN starts doing something weird on a W32 box, I personally would check those paths...
Cheers,
--- demerphq
my friends call me, usually because I'm late....
In reply to CPAN weirdness on Win32 by demerphq
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |