To whom it may concerned,
I'm trying to build a new R package in a windows platform.
Before that, I tried to check the previous well-know package from the CRAN
using the Rcmd command.
But I got the error messages as below.
I think this comes from the parsing error from the Perl script in
$RHOME/bin/check.
In the following example, 'Program Files' is splited into
'Program',
and this has made the R checking prosess halt.
What could I've done wrong?
---------------BELOW: ScreenShot from the windows console---------------
C:\Program Files\R\rw1080\src\library>Rcmd check qtl
* checking for working latex ...latex: not found
NO
C:/Program Files/R/rw1080/src/library
* using log directory 'C:/Program Files/R/rw1080/src/library/qtl.Rcheck'
* checking for file 'ChromoViz/DESCRIPTION' ... OK
* checking if this is a source package ... OK
Error: cannot change to directory `C:/Program'
ERROR
Installation failed.
---------------BELOW: Excerpt from the file $RHOME/bin/check ---------------
chdir($startdir);
$pkg =~ s/\/$//;
(-d $pkg) or die "Error: package dir '$pkg' does not
exist";
chdir($pkg)
or die "Error: cannot change to directory '$pkg'\n";
_________________________________________________________
Hoonie(Ji Hoon Kim)
SNUBI:Seoul National University Biomedical Informatics
+82-2-740-8318
On Mon, 17 Nov 2003 02:51:56 +0100 (CET), you wrote:>To whom it may concerned, > >I'm trying to build a new R package in a windows platform. >Before that, I tried to check the previous well-know package from the CRAN >using the Rcmd command. >But I got the error messages as below. >I think this comes from the parsing error from the Perl script in $RHOME/bin/check. >In the following example, 'Program Files' is splited into 'Program', >and this has made the R checking prosess halt. >What could I've done wrong?This is a known & documented problem, which we're unlikely to fix unless someone who experiences it submits a patch. The readme.packages file says this: "BEWARE: Don't expect this to work if the path to R_HOME contains spaces. It may work, but we don't recommend it." You seem to have one of the systems where it doesn't work. You should re-install R somewhere other than the "Program files" directory if you want this to work relatively painlessly. Duncan Murdoch
Just to add: the package to be checked has been unpacked in a path with spaces in _and_ Rcmd check was run from there. You could try just unpacking it in a more sensible place and running Rcmd check from there. On Sun, 16 Nov 2003, Duncan Murdoch wrote:> On Mon, 17 Nov 2003 02:51:56 +0100 (CET), you wrote: > > >To whom it may concerned, > > > >I'm trying to build a new R package in a windows platform. > >Before that, I tried to check the previous well-know package from the CRAN > >using the Rcmd command. > >But I got the error messages as below. > >I think this comes from the parsing error from the Perl script in $RHOME/bin/check. > >In the following example, 'Program Files' is splited into 'Program', > >and this has made the R checking prosess halt. > >What could I've done wrong? > > This is a known & documented problem, which we're unlikely to fix > unless someone who experiences it submits a patch. The readme.packages > file says this: > > "BEWARE: Don't expect this to work if the path to R_HOME contains > spaces. It may work, but we don't recommend it." > > You seem to have one of the systems where it doesn't work. You should > re-install R somewhere other than the "Program files" directory if you > want this to work relatively painlessly. > > Duncan Murdoch > > ______________________________________________ > R-devel@stat.math.ethz.ch mailing list > https://www.stat.math.ethz.ch/mailman/listinfo/r-devel > >-- Brian D. Ripley, ripley@stats.ox.ac.uk Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272866 (PA) Oxford OX1 3TG, UK Fax: +44 1865 272595