You can get around that immediate problem by copying the _Inline/config file from another location into the C:\Documents and Settings\_Inline folder - ie run an Inline::C script in (say) C:\nospaces, then copy C:\nospaces\_Inline\config across to the C:\Documents and Settings\_Inline folder.
But, with gcc at least, that only defers the problem. You'll get to the stage where
gcc -c -IC:/Documents and Settings ... gets run - but it needs to be run as something like
gcc -c "-IC:/Documents and Settings" ....
To fix that problem you need to hack at C.pm. There's a patch at
http://rt.cpan.org/Public/Bug/Display.html?id=4150 which you might find useful. I think (not sure) Eric Wilhelm has a build of Inline (google for Inline-0.44_01) that does permit the running of scripts inside directories with spaces.
For mine, the best solution is to not run Inline scripts in paths with spaces. In fact, one would be best advised to *never* enter such locations under any circumstances whatsoever.
Cheers,
Rob
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.