# from Sisyphus # on Monday 12 June 2006 09:44 pm: >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 ?
Eek. They come from the "fix" for spaces in the path :-( The issue is that (IIRC) $targetdir gets passed into the makefile. I'm guessing the above issue is actually happening on the other side of the makefile (after it's been generated.) It's been a while, so I just put my svn on the server. Feel free to checkout and/or see if the logs help. svn log http://scratchcomputing.com/x-Inline/local I'm suspecting this might be the culprit. Possibly something to do with how ExtUtils::Install functions on windows? Would escaping instead of quoting work? Maybe we should just use the c:\Docume~1\ directory :-) svn diff -r 6:7 http://scratchcomputing.com/x-Inline/local/C/C.pm (BTW: the changes to Inline.pm in that rev allowed the problem to get back to C.pm and then to the other side of the generated Makefile.PL where things start to blow-up during "make", IIRC.) Has anyone looked at using Module::Build inside Inline instead of ExtUtils::MakeMaker? Seems like "not printing makefiles" might clean things up a bit. --Eric -- As an old bass player friend of mine used to say: throw money, don't clap. --Tony Parisi --------------------------------------------------- http://scratchcomputing.com ---------------------------------------------------
