To close this thread, this issue appears to have been solved in R
devel since at least r57339 (also confirmed with r57348).
/Henrik
On Sun, Oct 16, 2011 at 5:58 AM, Henrik Bengtsson wrote:
> Hi.
>
> On Wed, Oct 12, 2011 at 9:24 AM, Joshua Wiley wrote:
>> Hi All,
>>
>> Apologies if this is a ver
Hi.
On Wed, Oct 12, 2011 at 9:24 AM, Joshua Wiley wrote:
> Hi All,
>
> Apologies if this is a very naive question. Is there a way to see the
> particular Rd file being processed right before a warning/error
> occurs? As far as I can tell, all my .Rd files use have names and
> titles and they ar
Hi Spencer,
Yes, I have versions that pass, but it is not package specific (i.e.,
I can download other package sources from CRAN and if I run R CMD
check on them, I get the same error). When I run R CMD check using R
2.13.1 or R 2.13.2 it is fine. Using either:
compiled from source:
R Under dev
le", mustWork=TRUE), "r")
Error in system.file(package = "base", "noSuchFile", mustWork = TRUE) :
no file found
Bill Dunlap
Spotfire, TIBCO Software
wdunlap tibco.com
> -Original Message-
> From: r-devel-boun...@r-project.org [mailto:r-devel-boun...
Hi, Josh:
Have you had a recent version that passed "R CMD check"? If yes,
I suggest you save your recent changes then revert to that earlier
version and add your recent changes back in again one at a time. I've
done that many times. (It's also a major reason I make changes as small
Thanks to Drs. Murdoch and Ripley for your fast and helpful replies.
I did not realize that R CMD check was R code, so that was incredibly
useful.
I spent the morning working on debugging this, and I think I must have
messed up setting up the Windows tool chain, because I get the error
even when r
R CMD check is R code: you can run the R code for yourself using R's
debugging facilities. In this case start with 'R CMD Rd2pdf pkg-name'
(which should give the same error, as that is what R CMD check calls),
then run that R code directly (there are comments in the code in
R-devel about how t
On 11-10-12 3:24 AM, Joshua Wiley wrote:
Hi All,
Apologies if this is a very naive question. Is there a way to see the
particular Rd file being processed right before a warning/error
occurs? As far as I can tell, all my .Rd files use have names and
titles and they are unique between Rd files (