From lawrencc at debian.org  Sun Feb 22 04:29:39 2004
From: lawrencc at debian.org (Chris Lawrence)
Date: Sun Feb 22 04:30:31 2004
Subject: [Rd] R CMD versus Rcmd
In-Reply-To: <403816A1.4050506@stat.auckland.ac.nz>
References: <e48f301rc2uvkcr7t3somsu7sus8ksrd2j@4ax.com>	<20040221201417.GA14135@sonny.eddelbuettel.com>
	<403816A1.4050506@stat.auckland.ac.nz>
Message-ID: <40382223.5090104@debian.org>

Ross Ihaka wrote:

> Dirk Eddelbuettel wrote:
>
>> On Sat, Feb 21, 2004 at 01:22:41PM -0500, Duncan Murdoch wrote:
>>
>>> I've just committed changes to R-devel (to become 1.9.0) to allow
>>> scripts to be invoked using the Unix-style "R CMD command" in Windows.
>>> "Rcmd command" will still work, but is no longer documented.
>>
>
> [ I don't seem to have the original handy ]
>
> This seems to have broken builds under linux (at least on Fedora).
> I get a string of messages of the form
>
> /home/ihaka/R/bin/R CMD: /home/ihaka/R/bin/R CMD: No such file or 
> directory
>
> I am currently working around this by changing lines in
> src/scripts/R.sh from
>
>       exec sh "${R_HOME}/bin/R CMD" "${@}" ;;
>
> to
>
>       exec sh "${R_HOME}/bin/Rcmd" "${@}" ;;
>
> between "configure" and "make".


Probably the ideal solution is:

exec sh "${R_HOME}/bin/R" CMD "${@}" ;;

Otherwise, sh tries to interpret the first argument as a pathname (i.e. 
looking for "R CMD" in that directory, rather than treating the space as 
an argument separator).


Chris


[Rd] R CMD versus Rcmd
Chris Lawrence