RE: Errors during dmake test, after building perl 5.8.6

2005-01-03 Thread Robert Johnson
Sisyphus wrote: Robert Johnson wrote: Hmm. I tried doing a `type filename.txt`, and perl always returns filename.txt not found (note: filename.txt does exist in the working directory, and entering type filename.txt from the MS command window prompt works as designed)

Re: Errors during dmake test, after building perl 5.8.6

2005-01-03 Thread Sisyphus
Robert Johnson wrote: Sisyphus wrote: Robert Johnson wrote: Hmm. I tried doing a `type filename.txt`, and perl always returns filename.txt not found Was that the full error statement ? Maybe there was more: sh: type: filename.txt not found That's what I get when I enter the command in an MSYS

Build warnings and test failures for perl 5.8.6

2005-01-03 Thread Robert Johnson
Sisyphus(Rob), et. al., This is my second try to build the stable perl -- same problems. New thread for clarity. I'm building Perl 5.8.6 again on my Windows XP box (factory Dell dimension 2yrs old standard stuff). Compiled it with with MinGW (3.1.0) using dmake (4.1 for win32). I'm still

Re: Build warnings and test failures for perl 5.8.6

2005-01-03 Thread Randy W. Sims
Robert Johnson wrote: Sisyphus(Rob), et. al., This is my second try to build the stable perl -- same problems. New thread for clarity. I'm building Perl 5.8.6 again on my Windows XP box (factory Dell dimension 2yrs old standard stuff). Compiled it with with MinGW (3.1.0) using dmake (4.1

RE: Errors during dmake test, after building perl 5.8.6

2005-01-03 Thread Robert Johnson
Sisyphus wrote: Was that the full error statement ? Maybe there was more: sh: type: filename.txt not found No. Just filename.txt not found if ($^O eq 'MSWin32') returns true, then the cmd.exe system commands will be available. Other windows system commands do work. Like `rename

Lloyd Prindle/GL/KSC/KeyCorp is out of the office.

2005-01-03 Thread Lloyd_Prindle
I will be out of the office starting 01/03/2005 and will not return until 01/04/2005. Please contact Joe Trunkett or Steve Yambor with any infrastructure issues in Cleveland. *** This communication may contain

Re: Errors during dmake test, after building perl 5.8.6

2005-01-03 Thread Sisyphus
Robert Johnson wrote: Sisyphus wrote: Was that the full error statement ? Maybe there was more: sh: type: filename.txt not found No. Just filename.txt not found if ($^O eq 'MSWin32') returns true, then the cmd.exe system commands will be available. Other windows system commands do work. Like

Backticks and the cmd.exe shell

2005-01-03 Thread Sisyphus
Hi, Suppose I have a file somewhere in my path named 'dir.exe' (that prints Gotcha! when executed). I also have a perl script, in which I want to capture the output of running the 'dir' shell command. So I write: my $out = `dir`; Unfortunately, $out contains the output of running 'dir.exe'.

Re: Backticks and the cmd.exe shell

2005-01-03 Thread $Bill Luebkert
Sisyphus wrote: Hi, Suppose I have a file somewhere in my path named 'dir.exe' (that prints Gotcha! when executed). I also have a perl script, in which I want to capture the output of running the 'dir' shell command. So I write: my $out = `dir`; Unfortunately, $out contains the

Re: Backticks and the cmd.exe shell

2005-01-03 Thread Sisyphus
Unfortunately, $out contains the output of running 'dir.exe'. How do I code it so that $out captures the output of running the 'dir' shell command, rather than the output of running 'dir.exe' ? Have you tried : my $out = `cmd /C dir`; No, I didn't - mainly because '/C' does not appear as an option

RE: Backticks and the cmd.exe shell

2005-01-03 Thread Jan Dubois
On Mon, 03 Jan 2005, Sisyphus wrote: Have you tried : my $out = `cmd /C dir`; No, I didn't - mainly because '/C' does not appear as an option in 'cmd command' under Windows Help. I did try a few other switches which *were* mentioned there (such as '/c' and '/k') but they didn't work as

Re: Backticks and the cmd.exe shell

2005-01-03 Thread Sisyphus
Jan Dubois wrote: On Mon, 03 Jan 2005, Sisyphus wrote: Have you tried : my $out = `cmd /C dir`; No, I didn't - mainly because '/C' does not appear as an option in 'cmd command' under Windows Help. I did try a few other switches which *were* mentioned there (such as '/c' and '/k') but they didn't