Hello Ivan.
The Does list.files(pattern = 'utils|Rout\\.fail') gave me something like
an empty string.
So after getting some in-person help on this issue, the key to resolving
this error was explicitly defining the environmental variables in the
console as:
set
On Mon, 26 Sep 2022 10:50:01 -0700
Edward Wei wrote:
> 1. Where do I run "make check"?
In the directory where R is built from source. If you're using a binary
build of R, this isn't applicable.
> 3. I get this back when I run the "tools::testInstalledPackages(scope
> = "base")" on my RGUI.
>
So I am looking at the R Installation and Administration section,
specifically section 3 for windows. . I have some inquiries.
1. Where do I run "make check"?
2. I got this when I was running the make check:
C:\Users\edmon\Documents\R\RFIN> R CMD make check
make: *** No rule to make target
On 16.09.2022 20:17, Edward Wei wrote:
That is an interesting thought. I don't think I have downloaded LaTex
explicitly, however, I do have MikTex and I added that file to PATH
manually.
This is what my current PATH calls:
On 9/16/22 20:17, Edward Wei wrote:
That is an interesting thought. I don't think I have downloaded LaTex
explicitly, however, I do have MikTex and I added that file to PATH
manually.
This is what my current PATH calls:
is not available“.
>
>
>
>
>
>
>
> *Von: *Edward Wei
> *Gesendet: *Mittwoch, 14. September 2022 22:26
> *An: *Matthias Gondan
> *Cc: *r-package-devel@r-project.org
> *Betreff: *Re: [R-pkg-devel] Unable to create manual
>
>
>
> Hello Matthias.
On 12.09.2022 15:09, Edward Wei wrote:
This is the following error message I get from R CMD check:
LaTeX errors when creating PDF version.
This typically indicates Rd problems.
* checking PDF version of manual without index ... ERROR
Re-running with no redirection of stdout/stderr.
Hmm ...
