similar to: Note: information on .o files is not available

I notice compositions was removed on CRAN, that's one I want to try out. I downloaded the last tarball, the build output doesn't look that bad. A warning, no errors. $ R CMD build compositions * checking for file ?compositions/DESCRIPTION? ... OK * preparing ?compositions?: * checking DESCRIPTION meta-information ... OK * cleaning src * checking for LF line-endings in source and make

Dear list, I have been checking my package ('analogue') using R2.13-0-alpha (details of exact svn version appended below) and the R CMD check procedure is generating an error rebuilding a vignette in the package, which raises a NOTE in the check. The log printed to screen during check shows: .... * checking re-building of vignettes ... NOTE Error in re-building vignettes: ... Error in

I'm trying to R CMD check a package, and I'm getting the 'checking S3 generic/method consistency' warning. I have written a function 'gamma.dist' which is _not_ an S3 method, but happens to collide with the 'gamma' function from the R::base namespace. Is there a way of telling CMD check that the name is intentional and is not meant to be an S3 method? My function

On CRAN, the package RSVGTipsDevice is only installed for 32bit Windows, and is not available as a 64bit package for Windows. The file linked to in the package check summary on CRAN says "NB: this package is only installed for sub-architecture 'i386' ". What do I need to do to make it available as both 64bit and 32bit on CRAN? (I am the maintainer of the package). It builds,

R gurus: I'm trying to get another round of rconifers out and I need some advice/help crushing differences in the examples test. I'm trying to make sure the max sdi values are being respected. I've added a tests/rconifers-Ex.Rout.save (from windows i386-pc-mingw32) and when I ran R CMD check (both R-2.13.0), I got the following results: * using log directory

Hi all I've been getting some emails from the R package maintainers that I need to update some code in a CRAN packge that uses FORTRAN, to comply with (not so recent) changes. I've been a little busy... I'm having trouble adjusting my code. I hope someone can help. The package was working fine, and a few R functions in my package had lines like this: tmp <- .Fortran(

Hello! I am updating to the R-devel version as of 2/28 and recompiling with OpenBLAS. I got that to compile nicely. I am now updating a package that uses the OpenBLAS and the PGI compiler, which has changed too. I just changed the path names in Makevars. Here is the Makevars file. FC= d:/PGI/win64/18.10/bin/pgf90 F77= d:/PGI/win64/18.10/bin/pgf90 CC = d:/PGI/win64/18.10/bin/pgcc FFLAGS=

I am trying someone's example to build a R package, but I get some errors, Can someone help me to figure it out? thanks, * using log directory '/home/aiminy/myrpackages/roots.Rcheck' * using R version 2.6.1 (2007-11-26) * checking for file 'roots/DESCRIPTION' ... OK * this is package 'roots' version '0.1-1' * checking package dependencies ... OK * checking if

I am getting the following problem with make check-all on the June 24 rc. I realize I could probably fix it by installing/setting a path to the sty file, but I don't remember having to do that for make check-all in the past. Paul Gilbert ___________ .... checking package 'Matrix' * checking for working pdflatex ... OK * using log directory

Dirk, thank you a thousand times. Indeed, src/Makevars was wrong. I modified Makevars so that now looks like the below and the package now compiled and linked properly. CXX_STD = CXX11 PKG_LIBS += $(SHLIB_OPENMP_CXXFLAGS) $(LAPACK_LIBS) $(BLAS_LIBS) $(FLIBS) $(shell ${R_HOME}/bin/Rscript -e "RcppParallel::RcppParallelLibs()") PKG_CXXFLAGS = $(SHLIB_OPENMP_CXXFLAGS) -I../inst/include

[Hope this is the right list where to send...] An attempt to update package 'mnormt' involves the addition of a small new function called 'pd.solve'. When I come to the package checking stage, an error occurs in parsing pd.solve.Rd. The full transcript of the outcome is copied below (it includes details on my installation) but the critical point is where the \examples{} section

When I build one of my packages with alpha from yesterday I am getting * checking for portable use of $BLAS_LIBS ... WARNING apparently missing $(FLIBS) in 'PKG_LIBS=$(LAPACK_LIBS) $(BLAS_LIBS)' Is this something I should worry about? (Possibly I got this before and didn't notice.) Paul Gilbert ====================================================================================

This is a bug/misfeature report for R CMD check. The function tools:::.check_packages_used_in_tests Gives an apparently unintended error when checking the tests in the contributed package rcdd_1.1-3.tar.gz as found on CRAN. See the script below for details. The actual error reported is totally mysterious. * checking for unstated dependencies in tests ... NOTE Error in

Hi, I don't know if I'm sending this to the right place but I've looked throught tens and tens of topics on http://tolstoy.newcastle.edu.au/ and finally found that email address where I can maybe find some help. Well my main goal is to get to use the lapack library within my R package (which can be done using calls from C). But in order to do this I have to create a file src/Makevars

Hi, I don't know if I'm sending this to the right place but I've looked throught tens and tens of topics on http://tolstoy.newcastle.edu.au/ and finally found that email address where I can maybe find some help. Well my main goal is to get to use the lapack library within my R package (which can be done using calls from C). But in order to do this I have to create a file src/Makevars

Hey Everyone, I'm running R 2.4.0 on Debian etch 4.0, and I'm trying to call some LAPACK functions from the C code in my package. Actually, to be honest I'm not really having trouble using commands such as La_dgesv from within my C code, but I do get warning when compiling the package saying: ***.c: In function '***': ***.c:37: warning: implicit declaration of function

When I install an R package with cpp codes such as rrcov via CRAN (under R 3.1.1, using no Makevars file and under Ubuntu 14.04 using GCC 4.8), the cpp code is compiled with the -o3 flag (in fact, looking at the Makeconf file this seem to again be the default since R 3.1.1) But when I install my own package via CRAN it is compiled with the -o2 flag. My questions are what is causing my

I am getting an error that I don't understand from R CMD check on my current instance of the survival code. R2.7.1 on Linux. Here is the last of the log * checking line endings in Makefiles ... OK * checking for portable use of $BLAS_LIBS ... OK * creating survival-Ex.R ... OK * checking examples ... OK * checking tests ... make[1]: Entering directory

Dear all, I am running R : Copyright 2005, Version 2.2.1 (2005-12-20 r36812) ISBN 3-900051-07-0 On a mac 10.4.5 I am having trouble with my package. The trouble is the following: In my package I have integrated three files in my src folder. 1- simplematch.C a .C file 2- ordering.f a fortran file 3- Makevars : PKG_LIBS = $(LAPACK_LIBS) $(BLAS_LIBS) $(FLIBS) I am not sure if that last file is

Dear helpers, I am trying to create a library which uses some Fortran source files and Lapack and Blas subroutines. The Fortran source files from the original author contain subroutines isamax.f, sgefa.f and sgesl.f, which are part of BLAS subroutines on my Linux computer, but maybe different (old) versions. So in addition to these subroutines, there are other Lapack and Blas subroutines