[R-pkg-devel] Different behavior from devtools::check and install.packages() under Linux and Windows
I have an R package that completes devtools::check() without errors,
warnings or notes running under Linux Mint, so I thought that all was
well. Everything works as expected when the package is installed on the
Linux box from GitHub.
However, when I attempt to install it on a Windows box I get:
R> devtools::install_github("sgutreuter/screenr")
Downloading GitHub repo sgutreuter/screenr@HEAD
Error: Failed to install 'screenr' from GitHub:
Multiple results for CXX11FLAGS found, something is wrong.FALSE
Next I tried devtools::check on clone on that same Windows box, and I gott:
R> devtools::check()
i Updating screenr documentation
i Loading screenr
Writing NAMESPACE
Writing NAMESPACE
-- Building -
screenr --
Setting env vars:
* CFLAGS : -Wall -pedantic -fdiagnostics-color=always
* CXXFLAGS : -Wall -pedantic -fdiagnostics-color=always
* CXX11FLAGS: -Wall -pedantic -fdiagnostics-color=always
Error in set_makevars(.new, .path, makevars_file, assignment =
.assignment) :
Multiple results for CXX11FLAGS found, something is wrong.FALSE
The strange (to me) thing is that the package is 100% R, so I don't
understand why C compiler flags are even in play. Earlier versions
worked as expected under both Linux and Windows.
Any hints?
Thanks!
--
Steve Gutreuter
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Cannot find source of devtool::check() warnings in R code
Thank you!!! On 12/9/21 11:16 AM, Uwe Ligges wrote: On 09.12.2021 17:10, Steve Gutreuter wrote: I am getting the following warnings from devtools:check(): W checking whether package ‘screenr’ can be installed (4.8s) Found the following significant warnings: Warning: replacing previous import ‘pROC::cov’ by ‘stats::cov’ when loading ‘screenr’ Warning: replacing previous import ‘pROC::var’ by ‘stats::var’ when loading ‘screenr’ Warning: replacing previous import ‘pROC::smooth’ by ‘stats::smooth’ when loading ‘screenr’ See ‘/tmp/RtmppuzDGj/screenr.Rcheck/00install.out’ for details. You import from NAMESPACEs pROC and stats, both offering functions of the same name. That means you should only import selectively from these NAMESPACEs what you need. Best, Uwe Ligges The 00install.out file does not inform me about where, in my R code, those warnings were triggered. I have searched my code for instances of *cov, *var and *smooth and found nothing. I suspect that the warnings are coming from functions from the stats package. Any hints about how to trace those warnings or, better yet, overcome them will me much appreciated -- Steve Gutreuter __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
[R-pkg-devel] Cannot find source of devtool::check() warnings in R code
I am getting the following warnings from devtools:check(): W checking whether package ‘screenr’ can be installed (4.8s) Found the following significant warnings: Warning: replacing previous import ‘pROC::cov’ by ‘stats::cov’ when loading ‘screenr’ Warning: replacing previous import ‘pROC::var’ by ‘stats::var’ when loading ‘screenr’ Warning: replacing previous import ‘pROC::smooth’ by ‘stats::smooth’ when loading ‘screenr’ See ‘/tmp/RtmppuzDGj/screenr.Rcheck/00install.out’ for details. The 00install.out file does not inform me about where, in my R code, those warnings were triggered. I have searched my code for instances of *cov, *var and *smooth and found nothing. I suspect that the warnings are coming from functions from the stats package. Any hints about how to trace those warnings or, better yet, overcome them will me much appreciated -- Steve Gutreuter __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Building fails with 'mypackage/DESCRIPTION' does not exist
Thank you Gábor! That was the problem, and I learned from it. On 10/1/19 9:36 AM, Gábor Csárdi wrote: > Your ignore file changes make R (and roxygen) ignore all source files: > https://github.com/sgutreuter/screenr/commit/3eaa9280221aa9885b6c35a758a46fbb2fdb1e46#diff-bc92b187c74649b3e0a039784ff93b39 > > Undo the `#*` line. > > Gabor > > On Tue, Oct 1, 2019 at 2:26 PM Steve Gutreuter wrote: >> First, thank you Bill Dunlap, Peter Dalgaard and Max Turgeon, >> >> I edited (incompletely) the initial posting and failed to change screenr >> to mypackage. However that was not the source of the problem. >> Windows sysadmins cannot be convinced that paths containing white space >> are pure evil, but that is also not the problem because building also >> fails on a Linux Mint box that uses only sane file/directory names. >> Default installation from GitHub (sgutreuter/screenr) succeeds because >> the version in Master is OK. The version in branch fixROC fails. >> >> I think that the root of the problem is that the Rd files are not being >> created in /man. Roxygen2::roxygenize() is failing *silently* (another >> source of frustration). So I suspect the problem lies somewhere in the >> comments for one or more of the functions. I am trying to identify >> where from a diff, as Bill suggested. >> >> Best regards, >> Steve >> >> >> On 9/30/19 5:30 PM, William Dunlap wrote: >>> Will the package build if you back out the "minor changes"? If so, >>> what were the minor changes (show diff output)? >>> >>> Bill Dunlap >>> TIBCO Software >>> wdunlap tibco.com <http://tibco.com> >>> >>> >>> On Mon, Sep 30, 2019 at 12:24 PM Steve Gutreuter >> <mailto:sgutreu...@gmail.com>> wrote: >>> >>> I have a package which will no longer build after minor changes. The >>> problem occurs under both Windows 10 and Linux Mint. For example, >>> from a >>> Windows terminal I do: >>> >>> C:\Users\xyz\OneDrive - ORG\Computing\Devel> R CMD build screenr >>> >>> and I get: >>> >>> * checking for file 'mypackage/DESCRIPTION' ... OK >>> * preparing 'mypackage': >>> * checking DESCRIPTION meta-information ... OK >>> * installing the package to process help pages >>> * saving partial Rd database >>> Error in .read_description(ldpath) : >>> file 'mypackage/DESCRIPTION' does not exist >>> Execution halted >>> >>> So the first and third lines of output contradict the error >>> message, and of >>> course mypackage/DESCRIPTION does exist. I suspect the problem >>> has nothing >>> to do with the DESCRIPTION file, but have not found way to >>> identify the >>> actual problem in searches on StackOverflow and elsewhere. My .R >>> files in >>> mypackage/R contain Roxygen comments, and curiously >>> devtools::document() >>> adds nothing to mypackage/man. >>> >>> Any suggestions about how to debug or solve this problem? >>> >>> Thanks! >>> Steve >>> >>> [[alternative HTML version deleted]] >>> >>> __ >>> R-package-devel@r-project.org >>> <mailto:R-package-devel@r-project.org> mailing list >>> https://stat.ethz.ch/mailman/listinfo/r-package-devel >>> >> -- >> Steve Gutreuter >> >> >> [[alternative HTML version deleted]] >> >> __ >> R-package-devel@r-project.org mailing list >> https://stat.ethz.ch/mailman/listinfo/r-package-devel -- Steve Gutreuter [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Building fails with 'mypackage/DESCRIPTION' does not exist
First, thank you Bill Dunlap, Peter Dalgaard and Max Turgeon, I edited (incompletely) the initial posting and failed to change screenr to mypackage. However that was not the source of the problem. Windows sysadmins cannot be convinced that paths containing white space are pure evil, but that is also not the problem because building also fails on a Linux Mint box that uses only sane file/directory names. Default installation from GitHub (sgutreuter/screenr) succeeds because the version in Master is OK. The version in branch fixROC fails. I think that the root of the problem is that the Rd files are not being created in /man. Roxygen2::roxygenize() is failing *silently* (another source of frustration). So I suspect the problem lies somewhere in the comments for one or more of the functions. I am trying to identify where from a diff, as Bill suggested. Best regards, Steve On 9/30/19 5:30 PM, William Dunlap wrote: > Will the package build if you back out the "minor changes"? If so, > what were the minor changes (show diff output)? > > Bill Dunlap > TIBCO Software > wdunlap tibco.com <http://tibco.com> > > > On Mon, Sep 30, 2019 at 12:24 PM Steve Gutreuter <mailto:sgutreu...@gmail.com>> wrote: > > I have a package which will no longer build after minor changes. The > problem occurs under both Windows 10 and Linux Mint. For example, > from a > Windows terminal I do: > > C:\Users\xyz\OneDrive - ORG\Computing\Devel> R CMD build screenr > > and I get: > > * checking for file 'mypackage/DESCRIPTION' ... OK > * preparing 'mypackage': > * checking DESCRIPTION meta-information ... OK > * installing the package to process help pages > * saving partial Rd database > Error in .read_description(ldpath) : > file 'mypackage/DESCRIPTION' does not exist > Execution halted > > So the first and third lines of output contradict the error > message, and of > course mypackage/DESCRIPTION does exist. I suspect the problem > has nothing > to do with the DESCRIPTION file, but have not found way to > identify the > actual problem in searches on StackOverflow and elsewhere. My .R > files in > mypackage/R contain Roxygen comments, and curiously > devtools::document() > adds nothing to mypackage/man. > > Any suggestions about how to debug or solve this problem? > > Thanks! > Steve > > [[alternative HTML version deleted]] > > __ > R-package-devel@r-project.org > <mailto:R-package-devel@r-project.org> mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel > -- Steve Gutreuter [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
[R-pkg-devel] Building fails with 'mypackage/DESCRIPTION' does not exist
I have a package which will no longer build after minor changes. The problem occurs under both Windows 10 and Linux Mint. For example, from a Windows terminal I do: C:\Users\xyz\OneDrive - ORG\Computing\Devel> R CMD build screenr and I get: * checking for file 'mypackage/DESCRIPTION' ... OK * preparing 'mypackage': * checking DESCRIPTION meta-information ... OK * installing the package to process help pages * saving partial Rd database Error in .read_description(ldpath) : file 'mypackage/DESCRIPTION' does not exist Execution halted So the first and third lines of output contradict the error message, and of course mypackage/DESCRIPTION does exist. I suspect the problem has nothing to do with the DESCRIPTION file, but have not found way to identify the actual problem in searches on StackOverflow and elsewhere. My .R files in mypackage/R contain Roxygen comments, and curiously devtools::document() adds nothing to mypackage/man. Any suggestions about how to debug or solve this problem? Thanks! Steve [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
