[R-pkg-devel] "Setting LC_CTYPE=en_US.UTF-8" failed and "qpdf28.dll was not found" on Win 10
Michael Dewey
||@t@ @end|ng |rom dewey@myzen@co@uk
Fri Apr 1 11:59:57 CEST 2022
Dear Spencer
If I understand correctly your package sos does not have compiled code
so as someone suggested earlier you do not need Rtools at all. The only
drawback is that when I check my packages I get a note that it cannot
find qpdf but they all pass checks on CRAN (which obviously does have qpdf).
Michael
On 31/03/2022 22:58, Spencer Graves wrote:
> Hi, Tomas and Ivan:
>
>
> On 3/31/22 1:52 AM, Tomas Kalibera wrote:
>>
>> On 3/31/22 08:39, Ivan Krylov wrote:
>>> On Wed, 30 Mar 2022 16:46:52 -0500
>>> Spencer Graves <spencer.graves using effectivedefense.org> wrote:
>>>
>>>> I'm getting different errors with MINGW64 and "Git CMD" under Windows
>>>> 10
>>> All these shortcuts do is launch cmd.exe or bash, optionally after
>>> setting %PATH%, optionally in a non-standard terminal application.
>>> Evidently, something in the %PATH% set by the shortcuts conflicts with
>>> the R CMD check process.
>>>
>>> For a package that doesn't have any compiled code, there should be no
>>> need for these tricks. Just start cmd.exe (for example, using Win+R,
>>> "cmd", Enter), navigate to your package and run something like
>>> "C:\Program Files\R-version\bin\R.exe" CMD check sos_2.1-4.tar.gz.
>>>
>>> If you're still having problems, try editing your %PATH% and trimming
>>> anything you don't need from there.
>>>
>>> If you're sure you need a special shortcut to launch a command line to
>>> check your package in, try installing Rtools and performing checks from
>>> "Rtools bash".
>>
>> With Rtools42, you don't need to run the Rtools bash, either, to check
>> packages. You can use cmd.exe (or any other console/shell) or you can
>> run the checks from R (e.g. via tools::Rcmd). This has more details
>> for R 4.2 with Rtools42 (but the same applies to R-devel):
>>
>> https://cran.r-project.org/bin/windows/base/howto-R-4.2.html
>>
>> With Rtools40 and R 4.0-4.1, this is almost the same but you need to
>> adjust PATH in the running session of R (see 6.3.1 in R admin manual
>> for the respective R release).
>>
>> Best
>> Tomas
>
> Thanks. On March 29, I upgraded to the latest version of R, RStudio
> (free version), and installed rtools4.2. I now have "Rtools",
> "rtools40" and "rtools42" installed in the "C:\" root directory. In a
> terminal, I got "path", and noted that it does NOT contain anything
> matching "rtools".
>
>
> After reviewing "howto-R-4.3.html", I ran "tools::Rcmd('check
> sos_2.1-4.tar.gz')" as suggested there, with results given below. I
> have the sos package installed in "~Documents\R\sos\sos". I have an R
> project in "~Documents\R\sos", and I used devtools::load_all('sos') to
> get RStudio to recognize the package. With that, I pressed "Install and
> Restart" and then "Check", and got seemingly the same results as
> recorded below.
>
>
> What do you think?
> Thanks for the help.
> Spencer Graves
>
> p.s. On my Mac, "R CMD check sos_2.1-4.tar.gz" works fine, as does the
> check process from within RStudio. Something's wrong in my setup on my
> Windows machine.
>
>
> tools::Rcmd('check sos_2.1-4.tar.gz')
>
> > tools::Rcmd('check sos_2.1-4.tar.gz')
> * using log directory 'C:/Users/spenc/Documents/R/sos/sos.Rcheck'
> * using R version 4.1.3 (2022-03-10)
> * using platform: x86_64-w64-mingw32 (64-bit)
> * using session charset: ISO8859-1
> * checking for file 'sos/DESCRIPTION' ... OK
> * this is package 'sos' version '2.1-4'
> * checking package namespace information ... OK
> * checking package dependencies ... OK
> * checking if this is a source package ... OK
> * checking if there is a namespace ... OK
> * checking for executable files ... OK
> * checking for hidden files and directories ... OK
> * checking for portable file names ... OK
> * checking whether package 'sos' can be installed ... OK
> * checking installed package size ... OK
> * checking package directory ... OK
> * checking 'build' directory ... OK
> * checking DESCRIPTION meta-information ... OK
> * checking top-level files ... OK
> * checking for left-over files ... OK
> * checking index information ... OK
> * checking package subdirectories ... OK
> * checking R files for non-ASCII characters ... OK
> * checking R files for syntax errors ... OK
> * checking whether the package can be loaded ... OK
> * checking whether the package can be loaded with stated dependencies
> ... OK
> * checking whether the package can be unloaded cleanly ... OK
> * checking whether the namespace can be loaded with stated dependencies
> ... OK
> * checking whether the namespace can be unloaded cleanly ... OK
> * checking dependencies in R code ... OK
> * checking S3 generic/method consistency ... OK
> * checking replacement functions ... OK
> * checking foreign function calls ... OK
> * checking R code for possible problems ... OK
> * checking Rd files ... OK
> * checking Rd metadata ... OK
> * checking Rd cross-references ... OK
> * checking for missing documentation entries ... OK
> * checking for code/documentation mismatches ... OK
> * checking Rd \usage sections ... OK
> * checking Rd contents ... OK
> * checking for unstated dependencies in examples ... OK
> * checking sizes of PDF files under 'inst/doc' ...Warning in
> system2(qpdf, "--version", TRUE) :
> running command '"C:\Windows\System32\qpdf_bin\qpdf.exe" --version'
> had status 309
> Error: invalid version specification 'NA'
> Execution halted
>
>
> R version 4.1.3 (2022-03-10)
> Platform: x86_64-w64-mingw32/x64 (64-bit)
> Running under: Windows 10 x64 (build 19043)
>
> Matrix products: default
>
> locale:
> [1] LC_COLLATE=English_United States.1252
> [2] LC_CTYPE=English_United States.1252
> [3] LC_MONETARY=English_United States.1252
> [4] LC_NUMERIC=C
> [5] LC_TIME=English_United States.1252
>
> attached base packages:
> [1] stats graphics grDevices utils datasets
> [6] methods base
>
> other attached packages:
> [1] sos_2.1-4 brew_1.0-7
>
> loaded via a namespace (and not attached):
> [1] compiler_4.1.3 tools_4.1.3
>
>>
>>>
>
> ______________________________________________
> R-package-devel using r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel
>
--
Michael
http://www.dewey.myzen.co.uk/home.html
More information about the R-package-devel
mailing list