similar to: Problem with R_registerRoutines

Thanks a lot for your answer Jeroen! I should have mentioned that I had actually only checked with the win-builder, as I did not have R-devel installed on my computer. But based on your answer I installed R-devel locally on a Linux-server (Redhat), and the package could be checked without the NOTE. So you might be right that this is a windows issue. However, another package that I am maintaining

>>>>> <Jon.SKOIEN at ec.europa.eu> >>>>> on Fri, 23 Feb 2018 15:43:43 +0000 writes: > Thanks a lot for your answer Jeroen! > I should have mentioned that I had actually only checked with the win-builder, as I did not have R-devel installed on my computer. > But based on your answer I installed R-devel locally on a Linux-server

On Windows this warning may be a false positive if R cannot find "objdump.exe" which is required for this check. I think this is actually a bug in R because it should be looking for "objdump.exe" inside BINPREF (where gcc is) rather than on the PATH. Can you check if you get the same warning if you upload the package to https://win-builder.r-project.org ? On Fri, Feb 23,

Sorry, resending with correct subject line. I didn't find the development version of your package but the latest version archived on CRAN uses Rcpp, RcppArmadillo. Since the latest versions of Rcpp and Armadillo support registration, it may be something related to RcppAttributes() or similar. I think that you don't need to do registration manually. I had a similar problem but when I

I didn't find the development version of your package but the latest version archived on CRAN uses Rcpp, RcppArmadillo. Since the latest versions of Rcpp and Armadillo support registration, it may be something related to RcppAttributes() or similar. I think that you don't need to do registration manually. I had a similar problem but when I realised the above, I discarded everything

Thanks for your email. I try to change the name in lowercase but it conflicts with a C implementation also named halton. So I rename the C function halton2() and sobol2() while the Fortran function are HALTON() and SOBOL() (I also try lower case in the Fortran code). Unfortunately, it does not help since I get init.c:97:25: error: use of undeclared identifier 'halton_'; did you mean

Have you tried using tools:::package_native_routine_registration_skeleton()? If you don't like its output, you can easily edit its results and still avoid most pitfalls. Cheers, Jari Oksanen ________________________________________ From: R-devel <r-devel-bounces at r-project.org> on behalf of Berend Hasselman <bhh at xs4all.nl> Sent: 10 May 2017 09:48 To: Christophe Dutang Cc:

Hi, I'm trying to register my native routines using R_registerRoutines (...). I can compile the code, but the loader cannot resolve the symbol: undefined symbol: _Z18R_registerRoutinesP8_DllInfoPK12R_CMethodDefPK15R_CallMethodDefS3_S6 _ $ nm bgx.Rcheck/bgx/libs/bgx.so | grep R_registerRoutines U _Z18R_registerRoutinesP8_DllInfoPK12R_CMethodDefPK15R_CallMethodDefS3_S6

I just updated my Redhat EL systems to R-2.7.2, and tried to update my packages as well. Lattice is one that failed. What do I need to do? R version 2.7.2 (2008-08-25) > install.packages("lattice", repos = "http://cran.fhcrc.org/") Warning in install.packages("lattice", repos = "http://cran.fhcrc.org/") : argument 'lib' is missing: using

R Listers, One of the list contributors suggested I abandon attempts to build R-1.9.1 and focus on building R-2.3.1. I believe the main set of packages have been built properly (with some changes to the code) - however, when building the Recommended packages, the build fails. CODE CHANGES: ============= 1. My C compiler requires a ";" on line 589 of ..../src/main/printutils.c. Here

Registration of 'native routines' (entry points in compiled code loaded into R) has been available for over 14 years, but few packages make use of it (less than 10% of those on CRAN with compiled code). Registration has similar benefits to name spaces in R code: - it ensures that the routines used by .C, .Call etc are those in your package (without needing a PACKAGE argument). - it

I am writing bindings to the neural network simulator SNNS. At present I have used only .C interface, now I'm studying .Call interface. I have adapted the example from page 77 of r-exts.pdf, however, it crashes R. I use MingW as recommended by Duncan Murdoch. Please, tell me what I am missing. The code is below. Thank you. SEXP snns_getVersion(void) {SEXP version; char *v;

I have a use case with tcltk-package where I need to repeatedly call Tcl/Tk functions very quickly. For such purpose, the standard R-interface turned out to be too slow, and better option has been to call package's C-function dotTcl directly from my own C-code. Before R 4.4.0 it was possible to use getNativeSymbolInfo("dotTcl","tcltk")$address (or

>>>>> Jon Skoien <jon.skoien at jrc.ec.europa.eu> >>>>> on Wed, 7 Dec 2016 11:04:04 +0100 writes: > I would like to ask once more if this is reproducible also for others? > If yes, should I submit it as a bug-report? > Best, > Jon Please Windows users .. this is possibly only for you! Note that I do *not* see problems on

I recently noticed a change between R-3.3.3 and R-3.4.0 in the definition of the R_CMethodDef struct. typedef struct { const char *name; DL_FUNC fun; int numArgs; - R_NativePrimitiveArgType *types; - R_NativeArgStyle *styles; - } R_CMethodDef; I suspect this is the reason that packages installed by R-3.4.0 and loaded into R-3.3.3 will crash the

I asked Tomas. Apparently this works: getNativeSymbolInfo("dotTcl",PACKAGE=getLoadedDLLs()$tcltk) and the tcltk behavior was changed by r84265 | hornik | 2023-04-15 08:44:36 +0200 (Sat, 15 Apr 2023) | 1 line Try forcing symbols in ff calls. Index: library/tcltk/src/init.c =================================================================== --- library/tcltk/src/init.c

> ... reports that the fortran names of all the registered fortran functions are ?undocumented objects?... Those symbols should not be exported. In quantreg v5.33, NAMESPACE has 'exportPattern(".")'. Maybe it is a good time to remove that and export explicitly the symbols that are meant for export. Georgi Boshnakov ------------------------------ Message: 6 Date: Fri, 28

Hi, I have followed the recommended steps for creating a package (rctest). As of now, my goal is simply to understand how various pieces fit together. The package includes: (1) C code with source in sub-directories, compiled to create a static library. (a) There is a single C-struct (dns) a simple 'matrix': {int m; int n; double *d;} (b) C code to create random matrix of a certain size.

CRAN (and crantastic) updates this week New packages ------------ Updated packages ---------------- New reviews ----------- This email provided as a service for the R community by http://crantastic.org. Like it? Hate it? Please let us know: cranatic at gmail.com.

Hi, One of the functions I use needs to write to a temporary file, in the directory given by tempdir(). I want to change this from the standard one, as the file is too large for the drive. However, tempfile() doesnt seem to respect the environment variables when I change them with Sys.setenv(). In a fresh R-session: > Sys.getenv("TMP") [1]