Re: [R-pkg-devel] Package Submission: issues with R_registerRoutines', 'R_useDynamicSymbols'
Thanks everyone! -Vineetha From: Ege Rubak <ru...@math.aau.dk> Sent: Thursday, April 13, 2017 11:04:20 AM To: Zhian Kamvar; Vineetha Warriyar Kodalore Vijayan Cc: r-package-devel@r-project.org Subject: Re: [R-pkg-devel] Package Submission: issues with R_registerRoutines', 'R_useDynamicSymbols' Hi, A few extra comments are below. On 04/14/2017 12:46 AM, Zhian Kamvar wrote: > Hi, > >> On Apr 13, 2017, at 11:41 , Vineetha Warriyar Kodalore Vijayan >> <vineethawarriyar@ucalgary.ca >> <mailto:vineethawarriyar@ucalgary.ca>> wrote: >> >> Hi Ege, >> >> >> Thank you! >> >> In the init.c file, do I have to change 'void' to corresponding >> declaration? >> >> E.g: >> >> extern void F77_NAME(datacon)(void *, void *, void *, void *, void *, >> void *, void *, void *, void *, void *, void *); >> I don't think you need to change anything in the generated file. At least I didn't, and I believe Brian Ripley mentioned that the script generated fully working init files for hundreds or thousands of packages with compiled code and only needed manual changes for tens of packages when they tested it on CRAN. >> >> Also, how do I know the package passes the CRAN incoming feasibility >> as it does not show any warnings or notes on my R CMD CHECK --as-cran. >> Re submit and see again? >> > > You can use R-Hub as a way to check your package on the development > version: https://github.com/r-hub/rhub#readme If you have your package > on a public remote git repository, you can additionally set up a > continuous integration service like > travis-ci: https://docs.travis-ci.com/user/languages/r/ and use that to > check against devel. > I agree that R-Hub is a great solution, and I have used it several times myself. You can even just use the website to submit a package: https://builder.r-hub.io/advanced But the R interface is nice, so it is recommendable to install the rhub package. Alternatively, submitting to http://win-builder.r-project.org/ also lets you test under R-devel. Best, Ege > Best, > Zhian > >> >> Regards, >> >> Vineetha Warriyar >> >> >> From: R-package-devel <r-package-devel-boun...@r-project.org >> <mailto:r-package-devel-boun...@r-project.org>> on behalf of Ege Rubak >> <ru...@math.aau.dk <mailto:ru...@math.aau.dk>> >> Sent: Thursday, April 13, 2017 9:35:36 AM >> To: r-package-devel@r-project.org <mailto:r-package-devel@r-project.org> >> Subject: Re: [R-pkg-devel] Package Submission: issues with >> R_registerRoutines', 'R_useDynamicSymbols' >> >> Hi, >> >> This is something that has gotten quite a bit of attention recently due >> to the coming R 3.4 giving a NOTE when routines aren't declared. You >> should be able to find info on this list or elsewhere. >> Basically you need to make a file called e.g. init.c in your src/ with >> the appropriate code. This file can be auto-generated for you as >> described by Dirk here: >> http://dirk.eddelbuettel.com/blog/2017/03/30/#002_even_easier_package_registration >> >> Good luck! >> >> Ege >> >> On 04/13/2017 11:14 PM, Vineetha Warriyar Kodalore Vijayan wrote: >>> >>> Hi, >>> >>> >>> When I submitted my R package to CRAN, it didn't go through the >>> automatic incoming check, resulting the following NOTE. I tested on >>> my macOS with R CMD CHECK and R CMD --as-cran, both went through with >>> one NOTE ( Maintainer: NOTE). >>> >>> * checking compiled code ... NOTE >>> File 'EpiILM/libs/i386/EpiILM.dll': >>> Found no calls to: 'R_registerRoutines', 'R_useDynamicSymbols' >>> File 'EpiILM/libs/x64/EpiILM.dll': >>> Found no calls to: 'R_registerRoutines', 'R_useDynamicSymbols' >>> >>> It is good practice to register native routines and to disable symbol >>> search. >>> >>> See 'Writing portable packages' in the 'Writing R Extensions' manual. >>> >>> I did go through the manual (section 5.4), but didn't understand >>> much. Can someone help to resolve this issue? >>> >>> >>> Thanks, >>> >>> Vineetha >>> >>> >>> [[alternative HTML version deleted]] >>> >>> __ >>> R-package-devel@r-project.org mailing list >>> https://stat.ethz.ch/mailman/listinfo/r-package-devel >>> >> >> __ >> R-package-devel@r-project.org mailing list >> https://stat.ethz.ch/mailman/listinfo/r-package-devel >> >> [[alternative HTML version deleted]] >> >> __ >> R-package-devel@r-project.org mailing list >> https://stat.ethz.ch/mailman/listinfo/r-package-devel > [[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] Package Submission: issues with R_registerRoutines', 'R_useDynamicSymbols'
Hi Ege, Thank you! In the init.c file, do I have to change 'void' to corresponding declaration? E.g: extern void F77_NAME(datacon)(void *, void *, void *, void *, void *, void *, void *, void *, void *, void *, void *); Also, how do I know the package passes the CRAN incoming feasibility as it does not show any warnings or notes on my R CMD CHECK --as-cran. Re submit and see again? Regards, Vineetha Warriyar From: R-package-devel <r-package-devel-boun...@r-project.org> on behalf of Ege Rubak <ru...@math.aau.dk> Sent: Thursday, April 13, 2017 9:35:36 AM To: r-package-devel@r-project.org Subject: Re: [R-pkg-devel] Package Submission: issues with R_registerRoutines', 'R_useDynamicSymbols' Hi, This is something that has gotten quite a bit of attention recently due to the coming R 3.4 giving a NOTE when routines aren't declared. You should be able to find info on this list or elsewhere. Basically you need to make a file called e.g. init.c in your src/ with the appropriate code. This file can be auto-generated for you as described by Dirk here: http://dirk.eddelbuettel.com/blog/2017/03/30/#002_even_easier_package_registration Good luck! Ege On 04/13/2017 11:14 PM, Vineetha Warriyar Kodalore Vijayan wrote: > > Hi, > > > When I submitted my R package to CRAN, it didn't go through the automatic > incoming check, resulting the following NOTE. I tested on my macOS with R > CMD CHECK and R CMD --as-cran, both went through with one NOTE ( Maintainer: > NOTE). > > * checking compiled code ... NOTE > File 'EpiILM/libs/i386/EpiILM.dll': > Found no calls to: 'R_registerRoutines', 'R_useDynamicSymbols' > File 'EpiILM/libs/x64/EpiILM.dll': > Found no calls to: 'R_registerRoutines', 'R_useDynamicSymbols' > > It is good practice to register native routines and to disable symbol > search. > > See 'Writing portable packages' in the 'Writing R Extensions' manual. > > I did go through the manual (section 5.4), but didn't understand much. Can > someone help to resolve this issue? > > > Thanks, > > Vineetha > > >[[alternative HTML version deleted]] > > __ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel > __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
[R-pkg-devel] Package Submission: issues with R_registerRoutines', 'R_useDynamicSymbols'
Hi, When I submitted my R package to CRAN, it didn't go through the automatic incoming check, resulting the following NOTE. I tested on my macOS with R CMD CHECK and R CMD --as-cran, both went through with one NOTE ( Maintainer: NOTE). * checking compiled code ... NOTE File 'EpiILM/libs/i386/EpiILM.dll': Found no calls to: 'R_registerRoutines', 'R_useDynamicSymbols' File 'EpiILM/libs/x64/EpiILM.dll': Found no calls to: 'R_registerRoutines', 'R_useDynamicSymbols' It is good practice to register native routines and to disable symbol search. See 'Writing portable packages' in the 'Writing R Extensions' manual. I did go through the manual (section 5.4), but didn't understand much. Can someone help to resolve this issue? Thanks, Vineetha [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
[R-pkg-devel] Makevar file issue.
Dear R package developers, I have developed an R package and its working locally on my system ( mac os x El Capitan, Xcode 7, gfortran 6.1) with ~/.R/Makevars. The Makevar file in the home directory contains: F77 = gfortran FC = gfortran FLIBS = -L/usr/local/gfortran/lib Now I'm trying to make this package portable. How can I move this dependent Makevar file into my src folder? I tried to move the same, but got an error saying * installing *source* package 'pkgname' ... ** libs gfortran-4.8 -fPIC -Wall -g -O2 -c epidata.f95 -o epidata.o make: gfortran-4.8: No such file or directory make: *** [epidata.o] Error 1 I did go through the writing R extension manual, but with my limited knowledge I couldn't find any solution. Any help would be really appreciated. Thanks, Vineetha [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
[R-pkg-devel] How to create choices in a function call.
Dear R package developers, I'm trying to create a small R package that gives me an epidemic from different epidemic models. I have imported the source codes from fortran for different models, say epidata1(),epidata2() and so on and it works fine. My question here is, how I can do the same by calling one function in R, which gives me options to input different model formulas and corresponding parameters. I'm relatively new in R programming and package building. I googled a lot and read about S3 and S4 methods, but really couldn't figure out how/where to start. I would really appreciate any help/guidance. Thank you, Vineetha [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
[R-pkg-devel] Regarding Fortran 77/95 Codes for building R package
Hi, I'm new to programming and now trying to build a R package which uses Fortran 95 codes ( gfortran 6.1 compiler) with a view to submit to CRAN at some point of time. I did go through the "Writing R extension" manual and got an impression that the codes must be in FORTRAN 77. I would like to know if I can proceed with my fortran 95 codes or do I have to change everything into FORTRAN 77. I would really appreciate if you can provide a right direction how to proceed. Thank you, Vineetha [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
