On Fri, 26 Apr 2002, Sam Tregar wrote: > On Sat, 27 Apr 2002, migu wrote: > > > incpath='D:\Archivos de programa\Microsoft Visual Studio\VC98\Include' > > libpth=' "D:\Perl\lib\CORE" "D:\Archivos de programa\Microsoft Visual >Studio\VC98\lib"' > > Trying using paths without spaces. I wouldn't be surprised if that was a > problem.
This is indeed the problem. I submitted a bug report for this http://www.mail-archive.com/[email protected]/msg00786.html This was the word from Neil Watkiss: > Sarathy just fixed an age-old bug in system() that fixes most problems like > these. Download ActivePerl 630 to see the difference. > > For example: > > system('dir /w', 'foo', 'bar'); > > Before AP630, the result was the same as system(qw(dir /w foo bar)) -- which is > a mistake! It just did a split on whitespace and took the first element to be > the name of executable (and tried various extensions). But what if we now > have an initial argument with spaces? > > system('C:\Program Files\bar', 'foo', 'bar'); > > Then we actually run this: system(qw(C:\Program Files\bar foo bar)). > Obviously incorrect. ActivePerl 630 now handles this correctly, as should > bleadperl and whatever the next 5.6.* release will be. > > The short answer is this: if you don't feel like upgrading, don't use spaces > in paths. Here's a solution for you if you insist on not upgrading: > > use Win32; > my $apache_dir = Win32::GetShortPathName('C:\Program Files\Apache'); > system("$apache_dir\\bin\\something.exe"); > > As a comforting note, Perl doesn't just have this problem on Windows. If you > were to use spaces in Unix, you'd have just the same problems. Of course, > it's a cardinal sin to use spaces in filenames in Unix. But in theory... _______________________________________ Andy Adler, [EMAIL PROTECTED]
