Bug #448 for ExtUtils-MakeMaker: MakeMaker busted when perl is in C:\Program Files

Fri Apr 05 11:04:23 2002 mschwern [...] cpan.org - Ticket created

Subject:

MakeMaker busted when perl is in C:\Program Files

On Win32, when Perl is in C:\Program Files MakeMaker can't find itself. This is likely because find_perl is using `` which can't handle a path name with a space in it (how ironic). The propsal is to use system LIST and bypass the shell. But there's likely other problems due to having a space in the path name. It may be necessary to convert it to the short DOS filename (ie. PROGRA~1).

Wed Nov 13 17:10:10 2002 mschwern [...] cpan.org - Correspondence added

[MSCHWERN - Fri Apr 5 11:04:23 2002]: Show quoted text

> On Win32, when Perl is in C:\Program Files MakeMaker can't find itself. > This is likely because find_perl is using `` which can't handle > a path name with a space in it (how ironic). > > The propsal is to use system LIST and bypass the shell. But there's > likely other problems due to having a space in the path name. > It may be necessary to convert it to the short DOS filename > (ie. PROGRA~1).

This has been partially fixed in the latest snapshot. find_perl() now handles perl with spaces in the filename.

Wed Nov 13 17:10:14 2002 mschwern [...] cpan.org - Status changed from 'new' to 'open'

Sat Dec 07 20:31:49 2002 mschwern [...] cpan.org - Correspondence added

[MSCHWERN - Wed Nov 13 17:10:10 2002]: Show quoted text

> > On Win32, when Perl is in C:\Program Files MakeMaker can't find

> itself.

This problem should be fully fixed in the latest snapshot. Perls with spaces in the name should work properly in all cases. Give the snapshot a shot, please.

Sat Dec 07 20:31:49 2002 mschwern [...] cpan.org - Status changed from 'open' to 'stalled'

Sat Dec 07 20:38:19 2002 mschwern [...] cpan.org - Correspondence added

[MSCHWERN - Sat Dec 7 20:31:49 2002]: Show quoted text

> [MSCHWERN - Wed Nov 13 17:10:10 2002]:

> > > On Win32, when Perl is in C:\Program Files MakeMaker can't find

> > itself.

> > This problem should be fully fixed in the latest snapshot. Perls with > spaces in the name should work properly in all cases. > > Give the snapshot a shot, please.

Oh, well... the new bottleneck is Test::Harness. Its not safe with perls with spaces in it. So 'make test' will probably not work. Well, try it anyway.

Sat Dec 07 20:38:20 2002 The RT System itself - Status changed from 'stalled' to 'open'

Sat Dec 21 21:32:35 2002 mschwern [...] cpan.org - Correspondence added

The fix doesn't work on Windows, which defeats the purpose. "C:\foo\bar\bin\perl" works fine from command.com and cmd.exe, but not inside nmake for some reason. `"$program" ...` is also causing trouble. We tried, but I'm going to have to declare this bug as not being worth the trouble.

Sat Dec 21 21:32:36 2002 mschwern [...] cpan.org - Status changed from 'open' to 'stalled'

Sat Jul 05 10:25:57 2003 The RT System itself - Status changed from 'stalled' to 'open'

Sat Jul 05 10:25:57 2003 Guest - Correspondence added

From:

Fabrice.Popineau [...] supelec.fr

[MSCHWERN - Sat Dec 21 21:32:35 2002]: Show quoted text

> The fix doesn't work on Windows, which defeats the purpose. > > "C:\foo\bar\bin\perl" works fine from command.com and cmd.exe, but

not Show quoted text

> inside nmake for some reason. `"$program" ...` is also causing > trouble. > > We tried, but I'm going to have to declare this bug as not being

worth Show quoted text

> the trouble.

It does worth the trouble IMHO. Microsoft guidelines for installing programs explicitely state that programs should be installed under "c:\Program Files". For myself, this "bug" prevented me to redistribute Perl as part of a free software project. I need to stick to ActiveState PerlApp compiler and redistribute scripts compiled as .exe files rather than embbed a full Perl distribution. With the drawback that users can't upgrade their scripts by themselves. On the other hand, I have thought a little bit about the problem and it does not seem easy to fix, because of the syntax involved. Fabrice Popineau

Sat Jul 05 17:27:01 2003 mschwern [...] cpan.org - Correspondence added

[guest - Sat Jul 5 10:25:57 2003]: Show quoted text

> > We tried, but I'm going to have to declare this bug as not being

> worth

> > the trouble.

> > It does worth the trouble IMHO. Microsoft guidelines for installing > programs explicitely state that programs should be installed > under "c:\Program Files".

Well, I'll be waiting for the patch from Microsoft then. :)

Tue Jul 15 17:53:08 2003 mschwern [...] cpan.org - Status changed from 'open' to 'stalled'

Thu Nov 25 22:00:47 2004 mschwern [...] cpan.org - Requestor burkhard.meier@gmx.de added

Thu Dec 09 18:00:05 2004 mschwern [...] cpan.org - Status changed from 'stalled' to 'open'

Thu Dec 09 18:00:05 2004 mschwern [...] cpan.org - Severity Important changed to Wishlist

Mon Mar 19 12:21:31 2012 https://www.google.com/accounts/o8/id?id=AItOawlVEP5IYeRHpH3ZT4ELVsJ3INWz0Lpegpo - Correspondence added

From:

Sam

At my workplace (restricted environment; perl under c:\Program Files), we currently work around the problem by post-processing the generating Makefile: 1) Run perl Makefile.PL 2) s///g in Makefile, replacing each "c:\Program Files" by "c:\Progra~1", as returned by Win32::GetShortPathName() 3) Run nmake Makefile Could this be done by ExtUtils::MakeMaker itself? Same as above, we tried just double-quoting the paths containing c:\Program Files, but it did not help.

Mon Jul 28 13:58:15 2014 ether [...] cpan.org - Reference by ticket #12713 added

Mon Jul 28 19:00:01 2014 ETJ [...] cpan.org - Correspondence added

I claim this is now obsolete since a) duplicate of RT-448; b) hopefully fixed in https://github.com/Perl-Toolchain-Gang/ExtUtils-MakeMaker/pull/105 -> 6.99_06.

Mon Jul 28 19:02:25 2014 rt-cpan [...] trout.me.uk - Status changed from 'open' to 'resolved'