Hi,
Check the thread "Inline on XP (and spaces in the path)" for some history.
The problem (when building Inline-0.44_01 on Win32):
------------------------------------------------------------------------
E:\comp_817\Inline-0.44_01>perl -Mblib C\t\01syntax.t
1..5
# Running under perl version 5.008008 for MSWin32
# Win32::BuildNumber 817
# Current time local: Tue Jun 13 13:22:38 2006
# Current time GMT: Tue Jun 13 03:22:38 2006
# Using Test.pm version 1.25
.
.
.
Uncaught exception from user code:
mkdir 'E:\: Invalid argument at E:/Perl817/lib/ExtUtils/Install.pm
line 112
dmake: Error code 150, while making 'pure_site_install'
.
.
-------------------------------------------------------------------
and installation fails.
It comes down to line 112 in the perl core module ExtUtils::Install.pm. That
line is:
mkpath($targetdir) unless $nonono;
With both 0.44 and 0.44_01, $nonono is set to zero - no problem there. But,
for me, with 0.44 $targetdir is set to:
E:\comp_817\Inline-0.44\_Inline_test\lib
whereas with 0.44_01 $targetdir is set to:
'E:\comp_817\Inline-0.44_01\_Inline_test\lib'
It's those single quotes surrounding the path that are killing the show.
Where do they come from, Eric ? What's the best way to fix ?
I dug a bit further and it seems those quotes kill ExtUtils::Install.pm in
quite a few places (line 112 is simply the first place that it's a problem).
This happens on all of my Win32 perl 5.8.8 builds - some MinGW-built, some
MSVC-built. I don't know if it affects earlier versions of Win32 perl.
Isn't it just easier to tell people not to do anything in directories that
contain spaces - except store documents and pictures - which is about all
they're good for ?
Cheers,
Rob
