- html - 出于某种原因,IE8 对我的 Sass 文件中继承的 html5 CSS 不友好?
- JMeter 在响应断言中使用 span 标签的问题
- html - 在 :hover and :active? 上具有不同效果的 CSS 动画
- html - 相对于居中的 html 内容固定的 CSS 重复背景?
我正在使用 Windows 并且刚刚更新到 R 4.0.3
(使用 RStudio
到 1.3.959
)并运行 R
检查我使用的软件包之一 Rcpp
和 RcppArmadillo
我得到以下注意:
> checking compiled code ... NOTE
Note: information on .o files for i386 is not available
Note: information on .o files for x64 is not available
File 'C:/Users/NIR_Workstation/Documents/GitHub/prospectr.Rcheck/prospectr/libs/i386/prospectr.dll':
Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
Found 'exit', possibly from 'exit' (C), 'stop' (Fortran)
Found 'printf', possibly from 'printf' (C)
File 'C:/Users/NIR_Workstation/Documents/GitHub/prospectr.Rcheck/prospectr/libs/x64/prospectr.dll':
Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
Found 'exit', possibly from 'exit' (C), 'stop' (Fortran)
Found 'printf', possibly from 'printf' (C)
当我在
R 4.0.2
下运行检查时,不会输出此注释.
R 4.0.3
):
Rcpp::Rcpp.package.skeleton("aTest", example_code = TRUE)
rcmdcheck::rcmdcheck(error_on = "warning", check_dir = "check")
我得到了与我的包的一个输出相同类型的 NOTE。再次为
R 4.0.2
这个注意不是输出。
R 4.0.3
在其他几台 Windows 机器中
rtools
,
RStudio
和
devtools
需要的包
reprex()
重现我为使用
Rcpp.package.skeleton()
创建的另一个模板包获得的注释:
mdir <- "./my_dir"
dir.create(mdir)
setwd("./my_dir")
Rcpp::Rcpp.package.skeleton("anotherTest", example_code = TRUE)
#> Creating directories ...
#> Creating DESCRIPTION ...
#> Creating NAMESPACE ...
#> Creating Read-and-delete-me ...
#> Saving functions and data ...
#> Making help files ...
#> Done.
#> Further steps are described in './anotherTest/Read-and-delete-me'.
#>
#> Adding Rcpp settings
#> >> added Imports: Rcpp
#> >> added LinkingTo: Rcpp
#> >> added useDynLib directive to NAMESPACE
#> >> added importFrom(Rcpp, evalCpp) directive to NAMESPACE
#> >> added example src file using Rcpp attributes
#> >> added Rd file for rcpp_hello_world
#> >> compiled Rcpp attributes
devtools::check("./anotherTest")
#> -- Building ----------------------------------------------------- anotherTest --
#> Setting env vars:
#> * CFLAGS : -Wall -pedantic
#> * CXXFLAGS : -Wall -pedantic
#> * CXX11FLAGS: -Wall -pedantic
#> --------------------------------------------------------------------------------
#> checking for file 'C:\Users\raml\AppData\Local\Temp\RtmpqMz20b\reprex4cd8438440a2\my_dir\anotherTest/DESCRIPTION' ... v checking for file 'C:\Users\raml\AppData\Local\Temp\RtmpqMz20b\reprex4cd8438440a2\my_dir\anotherTest/DESCRIPTION' (612ms)
#> - preparing 'anotherTest':
#> checking DESCRIPTION meta-information ... checking DESCRIPTION meta-information ... v checking DESCRIPTION meta-information
#> - cleaning src
#> - checking for LF line-endings in source and make files and shell scripts
#> - checking for empty or unneeded directories
#> - building 'anotherTest_1.0.tar.gz'
#>
#> -- Checking ----------------------------------------------------- anotherTest --
#> Setting env vars:
#> * _R_CHECK_CRAN_INCOMING_REMOTE_: FALSE
#> * _R_CHECK_CRAN_INCOMING_ : FALSE
#> * _R_CHECK_FORCE_SUGGESTS_ : FALSE
#> * NOT_CRAN : true
#> -- R CMD check -----------------------------------------------------------------
#> - using log directory 'C:/Users/raml/AppData/Local/Temp/RtmpCM99SH/anotherTest.Rcheck' (453ms)
#> - using R version 4.0.3 (2020-10-10)
#> - using platform: x86_64-w64-mingw32 (64-bit)
#> - using session charset: ISO8859-1
#> - using options '--no-manual --as-cran'
#> checking for file 'anotherTest/DESCRIPTION' ... checking for file 'anotherTest/DESCRIPTION' ... v checking for file 'anotherTest/DESCRIPTION'
#> - checking extension type ... Package
#> - this is package 'anotherTest' version '1.0'
#> checking package namespace information ... checking package namespace information ... v checking package namespace information
#> checking package dependencies ... checking package dependencies ... v checking package dependencies (1.4s)
#> checking if this is a source package ... v checking if this is a source package
#> v checking if there is a namespace
#> checking for executable files ... checking for executable files ... v checking for executable files (9.7s)
#> checking for hidden files and directories ... v checking for hidden files and directories
#> checking for portable file names ... checking for portable file names ... v checking for portable file names
#> v checking serialization versions
#> checking whether package 'anotherTest' can be installed ... checking whether package 'anotherTest' can be installed ... v checking whether package 'anotherTest' can be installed (29.5s)
#> checking installed package size ... checking installed package size ... v checking installed package size
#> v checking package directory
#> checking for future file timestamps ... checking for future file timestamps ... v checking for future file timestamps
#> checking DESCRIPTION meta-information ... checking DESCRIPTION meta-information ... v checking DESCRIPTION meta-information (689ms)
#> v checking top-level files
#> v checking for left-over files
#> v checking index information
#> checking package subdirectories ... checking package subdirectories ... v checking package subdirectories
#> checking R files for non-ASCII characters ... checking R files for non-ASCII characters ... v checking R files for non-ASCII characters
#> checking R files for syntax errors ... checking R files for syntax errors ... v checking R files for syntax errors
#> - loading checks for arch 'i386'
#> checking whether the package can be loaded ... checking whether the package can be loaded ... ** checking whether the package can be loaded ... OK
#> checking whether the package can be loaded with stated dependencies ... checking whether the package can be loaded with stated dependencies ... ** checking whether the package can be loaded with stated dependencies ... OK
#> checking whether the package can be unloaded cleanly ... checking whether the package can be unloaded cleanly ... ** checking whether the package can be unloaded cleanly ... OK
#> checking whether the namespace can be loaded with stated dependencies ... checking whether the namespace can be loaded with stated dependencies ... ** checking whether the namespace can be loaded with stated dependencies ... OK
#> checking whether the namespace can be unloaded cleanly ... checking whether the namespace can be unloaded cleanly ... ** checking whether the namespace can be unloaded cleanly ... OK
#> checking loading without being on the library search path ... checking loading without being on the library search path ... ** checking loading without being on the library search path ... OK
#> - loading checks for arch 'x64'
#> checking whether the package can be loaded ... checking whether the package can be loaded ... ** checking whether the package can be loaded ... OK
#> checking whether the package can be loaded with stated dependencies ... checking whether the package can be loaded with stated dependencies ... ** checking whether the package can be loaded with stated dependencies ... OK
#> checking whether the package can be unloaded cleanly ... checking whether the package can be unloaded cleanly ... ** checking whether the package can be unloaded cleanly ... OK
#> checking whether the namespace can be loaded with stated dependencies ... checking whether the namespace can be loaded with stated dependencies ... ** checking whether the namespace can be loaded with stated dependencies ... OK
#> checking whether the namespace can be unloaded cleanly ... checking whether the namespace can be unloaded cleanly ... ** checking whether the namespace can be unloaded cleanly ... OK
#> checking loading without being on the library search path ... checking loading without being on the library search path ... ** checking loading without being on the library search path ... OK
#> checking dependencies in R code ... checking dependencies in R code ... v checking dependencies in R code (475ms)
#> checking S3 generic/method consistency ... checking S3 generic/method consistency ... v checking S3 generic/method consistency (959ms)
#> checking replacement functions ... checking replacement functions ... v checking replacement functions (568ms)
#> checking foreign function calls ... checking foreign function calls ... v checking foreign function calls (575ms)
#> checking R code for possible problems ... checking R code for possible problems ... v checking R code for possible problems (4s)
#> checking Rd files ... checking Rd files ... v checking Rd files (375ms)
#> checking Rd metadata ... checking Rd metadata ... v checking Rd metadata
#> checking Rd line widths ... checking Rd line widths ... v checking Rd line widths
#> checking Rd cross-references ... checking Rd cross-references ... v checking Rd cross-references (364ms)
#> checking for missing documentation entries ... checking for missing documentation entries ... v checking for missing documentation entries (562ms)
#> checking for code/documentation mismatches ... checking for code/documentation mismatches ... v checking for code/documentation mismatches (1.8s)
#> checking Rd \usage sections ... checking Rd \usage sections ... v checking Rd \usage sections (1.3s)
#> checking Rd contents ... checking Rd contents ... v checking Rd contents
#> checking for unstated dependencies in examples ... checking for unstated dependencies in examples ... v checking for unstated dependencies in examples
#> checking line endings in C/C++/Fortran sources/headers ... v checking line endings in C/C++/Fortran sources/headers
#> checking pragmas in C/C++ headers and code ... checking pragmas in C/C++ headers and code ... v checking pragmas in C/C++ headers and code
#> v checking compilation flags used
#> checking compiled code ... checking compiled code ... N checking compiled code (27.9s)
#> Note: information on .o files for i386 is not available
#> Note: information on .o files for x64 is not available
#> File 'C:/Users/raml/AppData/Local/Temp/RtmpCM99SH/anotherTest.Rcheck/anotherTest/libs/i386/anotherTest.dll':
#> Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
#> Found 'exit', possibly from 'exit' (C), 'stop' (Fortran)
#> Found 'printf', possibly from 'printf' (C)
#> File 'C:/Users/raml/AppData/Local/Temp/RtmpCM99SH/anotherTest.Rcheck/anotherTest/libs/x64/anotherTest.dll':
#> Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
#> Found 'exit', possibly from 'exit' (C), 'stop' (Fortran)
#> Found 'printf', possibly from 'printf' (C)
#>
#> Compiled code should not call entry points which might terminate R nor
#> write to stdout/stderr instead of to the console, nor use Fortran I/O
#> nor system RNGs. The detected symbols are linked into the code but
#> might come from libraries and not actually be called.
#>
#> See 'Writing portable packages' in the 'Writing R Extensions' manual.
#> checking examples ... - checking examples (360ms)
#> running examples for arch 'i386' ... running examples for arch 'i386' ... ** running examples for arch 'i386' ... OK
#> running examples for arch running examples for arch 'x64' ... running examples for arch 'x64' ... ** running examples for arch 'x64' ... OK
#> v checking for non-standard things in the check directory
#> v checking for detritus in the temp directory
#>
#> See
#> 'C:/Users/raml/AppData/Local/Temp/RtmpCM99SH/anotherTest.Rcheck/00check.log'
#> for details.
#>
#>
#>
#> -- R CMD check results ------------------------------------ anotherTest 1.0 ----
#> Duration: 1m 31.9s
#>
#> > checking compiled code ... NOTE
#> Note: information on .o files for i386 is not available
#> Note: information on .o files for x64 is not available
#> File 'C:/Users/raml/AppData/Local/Temp/RtmpCM99SH/anotherTest.Rcheck/anotherTest/libs/i386/anotherTest.dll':
#> Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
#> Found 'exit', possibly from 'exit' (C), 'stop' (Fortran)
#> Found 'printf', possibly from 'printf' (C)
#> File 'C:/Users/raml/AppData/Local/Temp/RtmpCM99SH/anotherTest.Rcheck/anotherTest/libs/x64/anotherTest.dll':
#> Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
#> Found 'exit', possibly from 'exit' (C), 'stop' (Fortran)
#> Found 'printf', possibly from 'printf' (C)
#>
#> Compiled code should not call entry points which might terminate R nor
#> write to stdout/stderr instead of to the console, nor use Fortran I/O
#> nor system RNGs. The detected symbols are linked into the code but
#> might come from libraries and not actually be called.
#>
#> See 'Writing portable packages' in the 'Writing R Extensions' manual.
#>
#> 0 errors v | 0 warnings v | 1 note x
创建于 2020-10-18 由
reprex package (v0.3.0)
devtools::session_info()
#> - Session info ---------------------------------------------------------------
#> setting value
#> version R version 4.0.3 (2020-10-10)
#> os Windows 7 x64 SP 1
#> system x86_64, mingw32
#> ui RTerm
#> language (EN)
#> collate German_Switzerland.1252
#> ctype German_Switzerland.1252
#> tz Europe/Berlin
#> date 2020-10-18
#>
#> - Packages -------------------------------------------------------------------
#> package * version date lib source
#> assertthat 0.2.1 2019-03-21 [1] CRAN (R 4.0.3)
#> backports 1.1.10 2020-09-15 [1] CRAN (R 4.0.3)
#> callr 3.5.1 2020-10-13 [1] CRAN (R 4.0.3)
#> cli 2.1.0 2020-10-12 [1] CRAN (R 4.0.3)
#> crayon 1.3.4 2017-09-16 [1] CRAN (R 4.0.3)
#> desc 1.2.0 2018-05-01 [1] CRAN (R 4.0.3)
#> devtools 2.3.2 2020-09-18 [1] CRAN (R 4.0.3)
#> digest 0.6.26 2020-10-17 [1] CRAN (R 4.0.3)
#> ellipsis 0.3.1 2020-05-15 [1] CRAN (R 4.0.3)
#> evaluate 0.14 2019-05-28 [1] CRAN (R 4.0.3)
#> fansi 0.4.1 2020-01-08 [1] CRAN (R 4.0.3)
#> fs 1.5.0 2020-07-31 [1] CRAN (R 4.0.3)
#> glue 1.4.2 2020-08-27 [1] CRAN (R 4.0.3)
#> highr 0.8 2019-03-20 [1] CRAN (R 4.0.3)
#> htmltools 0.5.0 2020-06-16 [1] CRAN (R 4.0.3)
#> knitr 1.30 2020-09-22 [1] CRAN (R 4.0.3)
#> magrittr 1.5 2014-11-22 [1] CRAN (R 4.0.3)
#> memoise 1.1.0 2017-04-21 [1] CRAN (R 4.0.3)
#> pkgbuild 1.1.0 2020-07-13 [1] CRAN (R 4.0.3)
#> pkgload 1.1.0 2020-05-29 [1] CRAN (R 4.0.3)
#> prettyunits 1.1.1 2020-01-24 [1] CRAN (R 4.0.3)
#> processx 3.4.4 2020-09-03 [1] CRAN (R 4.0.3)
#> ps 1.4.0 2020-10-07 [1] CRAN (R 4.0.3)
#> R6 2.4.1 2019-11-12 [1] CRAN (R 4.0.3)
#> rcmdcheck 1.3.3 2019-05-07 [1] CRAN (R 4.0.3)
#> Rcpp 1.0.5 2020-07-06 [1] CRAN (R 4.0.3)
#> remotes 2.2.0 2020-07-21 [1] CRAN (R 4.0.3)
#> rlang 0.4.8 2020-10-08 [1] CRAN (R 4.0.3)
#> rmarkdown 2.4 2020-09-30 [1] CRAN (R 4.0.3)
#> rprojroot 1.3-2 2018-01-03 [1] CRAN (R 4.0.3)
#> rstudioapi 0.11 2020-02-07 [1] CRAN (R 4.0.3)
#> sessioninfo 1.1.1 2018-11-05 [1] CRAN (R 4.0.3)
#> stringi 1.5.3 2020-09-09 [1] CRAN (R 4.0.3)
#> stringr 1.4.0 2019-02-10 [1] CRAN (R 4.0.3)
#> testthat 2.3.2 2020-03-02 [1] CRAN (R 4.0.3)
#> usethis 1.6.3 2020-09-17 [1] CRAN (R 4.0.3)
#> withr 2.3.0 2020-09-22 [1] CRAN (R 4.0.3)
#> xfun 0.18 2020-09-29 [1] CRAN (R 4.0.3)
#> xopen 1.0.0 2018-09-17 [1] CRAN (R 4.0.3)
#> yaml 2.2.1 2020-02-01 [1] CRAN (R 4.0.3)
#>
#> [1] C:/Program Files/R/R-4.0.3/library
除了上述测试之外,我还运行了相同的代码:
R 4.0.3
与 rtools35
R 4.0.2
与 rtools40
R 4.0.3
在 linux ( x86_64-pc-linux-gnu (64-bit)
)R 4.0.3
与
rtools40
.这样对吗
rtools40
?如果是这样,对它的影响是什么
最佳答案
在过去的几个月里,我一直有同样的问题。几个月前,我在 Windows 的 R-devel 中注意到了同样的问题(中止的误报等)。
该问题并非特定于 Rcpp。我可以为仅包含 Fortran、仅包含 C 或仅包含 C++ 的包重现注释。我在 Windows 命令提示符下使用 Rtools40 和 R 4.0.3 在 PATH 中运行 R CMD。 NOTE 目前出现在 Bioconductor 3.12 检查数百个包中,似乎是包含任何 Fortran、C 或 C++ 源代码的任何包。正如您所指出的,NOTE 仅在 Windows、R 4.0.3 或更高版本和 Rtools40 中出现。对于 Linux 或 Mac 下的相同软件包或旧版本的 R,不会出现 NOTE 。
两天前我向 CRAN 提交了一个包,但 CRAN 没有将 NOTE 识别为问题,即使我在同一个包上运行 R CMD 检查时看到了 NOTE。所以我不认为它会导致你提交 CRAN 的问题。
关于r - 有关 x64 的 .o 文件的信息不可用 : NOTE on R package checks using Rcpp,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/64402688/
我在优化 JOIN 以使用复合索引时遇到问题。我的查询是: SELECT p1.id, p1.category_id, p1.tag_id, i.rating FROM products p1
我有一个简单的 SQL 查询,我正在尝试对其进行优化以删除“使用位置;使用临时;使用文件排序”。 这是表格: CREATE TABLE `special_offers` ( `so_id` int
我有一个具有以下结构的应用程序表 app_id VARCHAR(32) NOT NULL, dormant VARCHAR(6) NOT NULL, user_id INT(10) NOT NULL
此查询的正确索引是什么。 我尝试为此查询提供不同的索引组合,但它仍在使用临时文件、文件排序等。 总表数据 - 7,60,346 产品= '连衣裙' - 总行数 = 122 554 CREATE TAB
为什么额外的是“使用where;使用索引”而不是“使用索引”。 CREATE TABLE `pre_count` ( `count_id`
我有一个包含大量记录的数据库,当我使用以下 SQL 加载页面时,速度非常慢。 SELECT goal.title, max(updates.date_updated) as update_sort F
我想知道 Using index condition 和 Using where 之间的区别;使用索引。我认为这两种方法都使用索引来获取第一个结果记录集,并使用 WHERE 条件进行过滤。 Q1。有什
I am using TypeScript 5.2 version, I have following setup:我使用的是TypeScript 5.2版本,我有以下设置: { "
I am using TypeScript 5.2 version, I have following setup:我使用的是TypeScript 5.2版本,我有以下设置: { "
I am using TypeScript 5.2 version, I have following setup:我使用的是TypeScript 5.2版本,我有以下设置: { "
mysql Ver 14.14 Distrib 5.1.58,用于使用 readline 5.1 的 redhat-linux-gnu (x86_64) 我正在接手一个旧项目。我被要求加快速度。我通过
在过去 10 多年左右的时间里,我一直打开数据库 (mysql) 的连接并保持打开状态,直到应用程序关闭。所有查询都在连接上执行。 现在,当我在 Servicestack 网页上看到示例时,我总是看到
我使用 MySQL 为我的站点构建了一个自定义论坛。列表页面本质上是一个包含以下列的表格:主题、上次更新和# Replies。 数据库表有以下列: id name body date topic_id
在mysql中解释的额外字段中你可以得到: 使用索引 使用where;使用索引 两者有什么区别? 为了更好地解释我的问题,我将使用下表: CREATE TABLE `test` ( `id` bi
我经常看到人们在其Haxe代码中使用关键字using。它似乎在import语句之后。 例如,我发现这是一个代码片段: import haxe.macro.Context; import haxe.ma
这个问题在这里已经有了答案: "reduce" or "apply" using logical functions in Clojure (2 个答案) 关闭 8 年前。 “and”似乎是一个宏,
这个问题在这里已经有了答案: "reduce" or "apply" using logical functions in Clojure (2 个答案) 关闭 8 年前。 “and”似乎是一个宏,
我正在考虑在我的应用程序中使用注册表模式来存储指向某些应用程序窗口和 Pane 的弱指针。应用程序的一般结构如下所示。 该应用程序有一个 MainFrame 顶层窗口,其中有几个子 Pane 。可以有
奇怪的是:。似乎a是b或多或少被定义为id(A)==id(B)。用这种方式制造错误很容易:。有些名字出人意料地出现在Else块中。解决方法很简单,我们应该使用ext==‘.mp3’,但是如果ext表面
我遇到了一个我似乎无法解决的 MySQL 问题。为了能够快速执行用于报告目的的 GROUP BY 查询,我已经将几个表非规范化为以下内容(该表由其他表上的触发器维护,我已经同意了与此): DROP T
我是一名优秀的程序员,十分优秀!