From mboxrd@z Thu Jan  1 00:00:00 1970
Received: (from weis@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id TAA18224 for caml-redistribution; Tue, 30 Mar 1999 19:12:46 +0200 (MET DST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id RAA04413 for <caml-list@pauillac.inria.fr>; Tue, 30 Mar 1999 17:37:50 +0200 (MET DST)
Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35])
	by concorde.inria.fr (8.8.7/8.8.7) with ESMTP id RAA09253;
	Tue, 30 Mar 1999 17:37:47 +0200 (MET DST)
Received: (from xleroy@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id RAA29945; Tue, 30 Mar 1999 17:37:46 +0200 (MET DST)
Message-ID: <19990330173746.17768@pauillac.inria.fr>
Date: Tue, 30 Mar 1999 17:37:46 +0200
From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Stephanie Weirich <sweirich@cs.cornell.edu>, caml-list@inria.fr
Subject: Re: Sys.command in Windows NT
References: <19990329183317.59444@pauillac.inria.fr> <000201be7a22$f46180e0$61f85480@pittston.cs.cornell.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89.1
In-Reply-To: <000201be7a22$f46180e0$61f85480@pittston.cs.cornell.edu>; from Stephanie Weirich on Mon, Mar 29, 1999 at 03:30:15PM -0500
Sender: weis

> I'm unable to execute Sys.command under Windows NT.
> I get the error message:
> /c: Permission denied
> and a return value of 1.
> I'm sure that something is not configured correctly, but I'm not sure 
> where to look. 

First, check the environment variables COMSPEC and PATH in your
environment, because that's where the C library function system()
(which implements Sys.command) looks for the Windows command
interpreter.  On my installation of NT, for instance, I have
COMSPEC set to C:\winnt\system32\cmd.exe, which is NT's command interpreter.
If COMSPEC is unset, I think system() searches in PATH for cmd.exe or
command.exe.

If the environment variables look OK, but the command line given to
Sys.command is longer than 1000 characters, try first with shorter
commands.  Long command lines are treated specially by the OCaml
runtime, and there might be a problem there.

If that doesn't help, I don't know how to proceed.  As far as I know,
there is no Windows tool that would trace the system calls performed
by OCaml, so that we know exactly what is happening.

- Xavier Leroy