Many of the "tried and tested" tools of Perl have problems with spaces in directory names, most notably CPAN.pm, and Inline::C (not in the category "tried and tested"). I find this is especialy weird, because under Unix file names with whitespace are much longer allowed than in the Win32 world, and given the Unix-centricity of the developers, this should have been an issue a long time ago. It seems that nobody ever went and fixed the issues. I did once try to hunt down all the cases where CPAN.pm fails to do the Right Thing when (not) quoting filenames, but gave up.

So the moral of this is - don't install Perl below a directory with spaces in its name.

In reply to Re^3: Error When Making Pugs on Windows XP by Corion
in thread Error When Making Pugs on Windows XP by goober99

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.