Gerhard,

On 28 January 2020 at 15:28, Ralf Stubner wrote:
| On Tue, Jan 28, 2020 at 10:04 AM Gerhard Boenisch
| <boeni...@bgc-jena.mpg.de> wrote:
| > I am new to rcpp and am unable to compile code I know works. I must be 
doing something stupid.
| >
| > I am using Windows (10).
| >
| > I have received the cpp source files for the BHPMF package. We want to make 
the package work on the latest version of R.
| 
| I assume this refers to
| https://cran.r-project.org/src/contrib/Archive/BHPMF/BHPMF_1.0.tar.gz,
| right? Then this is actually off-topic on this list, since BHPMF does
| not use Rcpp. The r-pkg-devel mailing list might be more appropriate.

Uh-oh, please do not abuse the friendly nature of this list for non-related
topics.

There are r-help, StackOverflow, the excellent r-pkg-devel and more.

| > I am currently using R 3.4.4 (the last version BHPMF works).
| 
| I think you can work with a more recent version right away. Out of
| curiosity I ran
| 
| R CMD check BHPMF_1.0.tar.gz
| 
| using current R 3.6.2. This command compiles and installs the package
| and runs different checks on it. The result were two warnings:
| 
| * checking whether package ‘BHPMF’ can be installed ... WARNING
| Found the following significant warnings:
|   utillity.cpp:293:15: warning: ignoring return value of ‘int
| fscanf(FILE*, const char*, ...)’, declared with attribute
| warn_unused_result [-Wunused-result]
| [...]
| * checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... WARNING
|   apparently using $(BLAS_LIBS) without following $(FLIBS) in ‘src/Makevars’
| 
| Warnings like this this are sufficient to have a package removed from
| CRAN. They should be easy enough to fix, though.

r-pkg-devel seems like a good venue for general R package tips.

Good luck,  Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
_______________________________________________
Rcpp-devel mailing list
Rcpp-devel@lists.r-forge.r-project.org
https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel

Reply via email to