A possible work around for this type of problem is to use the Junction utility from MS or from sysinternals.com to cause
C:\Perl to actually be a junction against C:\Program Files At least thats how I handled it the one time I forgot and installed perl in \Program Files. So in your installation script create the junction first then install Perl into C:\Perl and your IT types will be happy becuase they will see it in C:\Program Files. Of course a smarter longer term approach would be to get them to change their rather stupid policy. Yves > -----Original Message----- > From: Tim Bunce [mailto:[EMAIL PROTECTED] > Sent: 13 January 2004 14:54 > To: Brian Campbell > Cc: Jonathan Leffler; BAFFIGI, Christian; DBI Users; > [EMAIL PROTECTED] > Subject: Space in installation directory name causes problems > > > On Mon, Jan 12, 2004 at 05:03:52PM -0700, Brian Campbell wrote: > > Some advice: Make sure your perl installation is not in the > "Program Files" > > or any directory that has a "space" in the name. I think > ActiveState Perl > > defaults > > Perl to an installation location of "C:\Perl", but per IT > policy at our > > site, our > > site-specific installation process places all apps in > "C:\Program Files", > > e.g. "C:\Program Files\Perl". > > > > The DBD make process makes several references to this path > but does not > > support blanks (that > > is, there are several points where the process breaks or > fails when it > > encounters such a path). > > Furthermore, the make process calls Perl utility packages > which use this > > path and I found that > > the packages don't support blanks either (same symptoms). > I managed to > > find and fix several of > > the "bugs" in the make code and Perl packages, and > developed work-arounds in > > other cases. > > This path issue accounted for the majority of build > problems I ran into. > > Please help "save the world" by sending fixes to the relevant people. > > Here for DBI and DBD Makefile.PL changes and [EMAIL PROTECTED] > for changes to ExtUtils::MakeMaker. Even if you can't fix the whole > problem any progress helps and also keeps the issue alive. > > Tim. > > p.s. You don't mention what version of perl you're using. The > situation > may be better with more recent versions. >
