I believe you've got _some_ time. As of the changes in 3.4.0 the verbiage is:
R CMD check --as-cran now NOTEs if the package does not register
its native routines or does not declare its intentions on (native)
symbol search. (This will become a WARNING in due course.)
And I think it's
Sorry. I am a moron. It was an illusion. I was checking R package
foo with the Makevars for R package fooRegister via the
R_MAKEVARS_USER mechanism and got confused. In fact R package foo,
when checked with --as-cran only gives warnings not errors about
registering native routines.
So AFAICS,
https://stat.ethz.ch/pipermail/r-devel/2017-February/073755.html
On Sat, Feb 16, 2019 at 3:22 PM Charles Geyer wrote:
>
> I just noticed that R package foo in the github repo
> https://github.com/cjgeyer/foo no longer passes R CMD check --as-cran. The
> problem seems to be that it does not regis
I just noticed that R package foo in the github repo
https://github.com/cjgeyer/foo no longer passes R CMD check --as-cran. The
problem seems to be that it does not register native routines and thus the
C routines cannot be found. It does pass R CMD check (without --as-cran).
The version of the p
Changing the path solved the problem. Thanks everyone!
Rampal
On 11-Apr-18 14:24, Marcelino de la Cruz Rot wrote:
Thank you for the hint, Henric.
I was also having the same NOTE.
Changing the path from \Rtools\mingw_32\bin to \Rtools\mingw_64\bin
solved it completely. Cheers, Marcelino
El
Thank you for the hint, Henric.
I was also having the same NOTE.
Changing the path from \Rtools\mingw_32\bin to \Rtools\mingw_64\bin
solved it completely. Cheers, Marcelino
El 11/04/2018 a las 11:56, Henric Winell escribió:
Den 2018-04-10 kl. 23:30, skrev Rampal Etienne:
Dear Thomas,
Yes,
On 10 April 2018 at 23:30, Rampal Etienne wrote:
| Yes, I followed all those suggestions but it did not fix the x64 notes.
| Indeed I am using Windows. I am going to try this on a Linux system.
You could consider the R Hub service at
https://builder.r-hub.io/
and/or via the CRAN package rh
Den 2018-04-10 kl. 23:30, skrev Rampal Etienne:
Dear Thomas,
Yes, I followed all those suggestions but it did not fix the x64 notes.
Indeed I am using Windows. I am going to try this on a Linux system.
On a 64-bit system you need to have 64-bit versions of the necessary
tools on the path, b
Dear Thomas,
Yes, I followed all those suggestions but it did not fix the x64 notes.
Indeed I am using Windows. I am going to try this on a Linux system.
Cheers, Rampal
On 10-Apr-18 14:17, Thomas Petzoldt wrote:
Hi,
I assume you followed "Writing R Extension" and the examples given in
pac
Hi,
I assume you followed "Writing R Extension" and the examples given in
package deSolve (and maybe some other packages).
Am I right that this fixed the i386 notes, but not for x64?
Here I conclude that you tested it on Windows. This is relevant, because
I remember a recent discussion (mayb
Dear all,
I am using Fortran code with the deSolve package in my package called
"DDD". When checking my package I get the message:
checking compiled code ... NOTE
File 'DDD/libs/x64/DDD.dll':
Found no calls to: 'R_registerRoutines', 'R_useDynamicSymbols'
It is good practice to register native
I am working on an update to my package pcaL1. Using win-builder, I
get a note including "Found no calls to 'R_registerRoutines',
'R_useDynamicSymbols'". However, in my submission, I have a file
src/init.c that includes the contents at the bottom of this email to
register .C() routines. Why can'
12 matches
Mail list logo
