Re: [R-pkg-devel] FW: [CRAN-pretest-archived] CRAN submission RIBMDB 1.0.0

Hi Ivan, Thanks for the response. Appreciate. But, 1. Windows: As I can see in the logs of the machine: platform = windows , arch = x64 , R_Version = R Under development (unstable) (2021-02-16 r80015) So that means the architecture on CRAN machine is 64 bit and not 32 bit. This is extr

[R-pkg-devel] Cannot reproduce CRAN error (Solaris i386)

Hello, I have a package on CRAN called 'metapack' and received a message from Professor Ripley that the error must be resolved for the package to be safely retained in CRAN. I've encountered this error on R-CMD-check on GitHub but cannot replicate it on any of my local machines to save my life. Th

Re: [R-pkg-devel] How to R CMD build / check using LTO

I suspect your problem is that, at least with the recent gnu compilers, the Fortran 'c_logical' maps to the C _Bool, not the C int. -Bill On Wed, Feb 17, 2021 at 11:38 AM Paul Schmidt-Walter wrote: > > Dear Team, > > My package 'LWFBrook90R' (https://github.com/pschmidtwalter/LWFBrook90R) > was

Re: [R-pkg-devel] How to R CMD build / check using LTO

You can use this Docker container: https://hub.docker.com/repository/docker/rhub/debian-gcc-devel-lto It is somewhat old, but chances are that it will reproduce the LTO issues. I'll update it in a minute, anyway. Gabor On Wed, Feb 17, 2021 at 9:33 PM Ivan Krylov wrote: > > On Wed, 17 Feb 2021 2

Re: [R-pkg-devel] How to R CMD build / check using LTO

On Wed, 17 Feb 2021 20:04:34 +0100 Paul Schmidt-Walter wrote: > I simply don't know how to "build with configure --enable-lto" "R Installation and Administration" contains a detailed set of instructions on how to compile R, includin

Re: [R-pkg-devel] FW: [CRAN-pretest-archived] CRAN submission RIBMDB 1.0.0

Hello Binit Kumar, On Wed, 17 Feb 2021 15:12:53 + Binit Kumar wrote: > Error: Ld:/Compiler/gcc-4.9.3/local330/lib > -LD:/RCompile/recent/R/bin/i386 -lR clidriver/bin/db2app64.dll: file > not recognized: file format not recognized > > Why is db2app64.dll a non recognized file? The package i

Re: [R-pkg-devel] Unicode errors when building a package

Thanks Max and Fernando, The Max's solution was the one worked for me. Thanks, All the best, Ibon El mié, 17 feb 2021 a las 20:14, Max Turgeon () escribió: > Hi Ibon, > > It looks like you have a couple non-ASCII characters in your documentation > files. You can find which ones by running the co

[R-pkg-devel] How to R CMD build / check using LTO

Dear Team, My package 'LWFBrook90R' (https://github.com/pschmidtwalter/LWFBrook90R) was recently released on CRAN, but there are additional LTO Issues (https://www.stats.ox.ac.uk/pub/bdr/LTO/LWFBrook90R.out) with the compiled code, that need to be fixed soon. I would like to reproduce the LT

Re: [R-pkg-devel] Unicode errors when building a package

Hi Ibon, It looks like you have a couple non-ASCII characters in your documentation files. You can find which ones by running the command showNonASCIIfile in the tools package. To address these warnings, you have two options: 1. Replace these non-ASCII characters with similar/equivalent ASC

Re: [R-pkg-devel] URL in RMarkdown file (libcurl error code 35)

Sorry, you can ignore my question: Uwe Liges clarified to me that the other error in my CRAN submission check is definitely a problem I need to address. And from this post by Hadley on Twitter I conclude that the URL warning can be ignored: https://twitter.com/hadleywickham/status/13581706073142353

[R-pkg-devel] Unicode errors when building a package

Dear all, I am trying to fix all the error of my package. Most of them I know how to solve them. But there are some errors related with unicode that I don't know how to fix. Flavor: r-devel-windows-ix86+x86_64 Check: PDF version of manual, Result: WARNING LaTeX errors when creating PDF version.

Re: [R-pkg-devel] URL in RMarkdown file (libcurl error code 35)

I suspect that this is an issue with the CRAN Windows machine, not with your package. If you want to work around it in the incoming checks, you can remove the URL. Maybe it is enough to remove the `https://` from the beginning, but I am not sure. Gabor On Wed, Feb 17, 2021 at 4:33 PM Vincent van

[R-pkg-devel] CRAN pre-test Windows machine seems to be in a bad state

In particular the magrittr package seems to be broken on the pre-test machine. I submitted a new version of the pkgload package on Friday, again on Tuesday and today (Wednesday). All passed fine on the Debian machine, but failed during installation on the Windows builder. The failure is due to a

[R-pkg-devel] URL in RMarkdown file (libcurl error code 35)

Hello, My R package submission got rejected today because of the URL libcurl error code 35 issue below (see heading Attempt 1). It seems I have a subscription to these errors, because I have been getting them a lot through the years. Next, I edited the URL and submitted the package to R-devel on wi

[R-pkg-devel] FW: [CRAN-pretest-archived] CRAN submission RIBMDB 1.0.0

Hi Team, I uploaded a package in CRAN and it failed with the attached error. My question: 1. Windows: Error: Ld:/Compiler/gcc-4.9.3/local330/lib -LD:/RCompile/recent/R/bin/i386 -lR clidriver/bin/db2app64.dll: file not recognized: file format not recognized Why is db2app64.dll a non recognized