Just as an incidental remark about Rcpp on FreeBSD, since that
Unix-alike OS is 'non standard' in some way ;-)
On 22.02.2011 18:55 (UTC+1), Dirk Eddelbuettel wrote:
On 22 February 2011 at 12:45, Simon Urbanek wrote:
|
| On Feb 22, 2011, at 12:32 PM, Dirk Eddelbuettel wrote:
|
|>
|> On 22 February 2011 at 11:26, ken.willi...@thomsonreuters.com wrote:
|> | On 2/22/11 11:13 AM, "Dirk Eddelbuettel"<e...@debian.org> wrote:
|> |>Just a quick note to say that ...
|> |>
|> |>On 22 February 2011 at 10:53, ken.willi...@thomsonreuters.com wrote:
|> |>| got farther, so now I'm getting correct output from it. BTW, I changed
|> |>| the prereq on Rcpp from 0.9.0 to 0.8.6 since that's the latest public
|> |>| release.
|> |>
|> |>... this ain't so. Are you running an old R version that looks into a
|> |>versioned subtree of CRAN? Rcpp is at 0.9.1, its Archive/ has the
|> |>history up
|> |>from 0.6.0. See http://cran.r-project.org/web/packages/Rcpp/index.html
|> |
|> | Oh! Looks like the GUI package installer in R.app was set to just show
|> | the latest OS X binary on CRAN, which is 0.8.6. Is there some reason
|> | that's trailing the source release?
|>
|> Crap, you're absolutely correct. Forgot about the OS X aspect, as well as my
|> mental note to bug Simon about the stone-old build, so doing that now.
|>
|> Simon: Are there are any reasons Rcpp is frozen on a version that is five
|> months old and five releases behind?
|>
|
| Yes, it's not passing checks - it's that simple:
| http://www.R-project.org/nosvn/R.check/r-prerel-macosx-ix86/Rcpp-00check.html
Tres etrange, as Romain develops on OS X himself. I will have to pass on this
one for lack of access to such shiny hardware. He may fix it, or he may not.
I vaguely recall us discussing that with you and Romain's inability to
reproduce it. As such, chances of improvement may be slim. Tant pis.
| And OS X is not the only place as you'll see when you look at
| http://cran.r-project.org/web/checks/check_results_Rcpp.html
I do look there regularly but I cannot fix Slowlaris and the funky SunOS
compiler messages until we get the rumoured 'bin-builder'.
Hints for shutting up R-devel on the 'size' NOTE concerning the arbitrary 1mb
cutoff (hey, "640kb should be enough for everyone" so why not use that?) would
be welcome too.
Dirk
I checked (and installed) Rcpp_0.9.1.tar.gz on FreeBSD 9.0-CURRENT
(amd64), the development version of FreeBSD. Compiler is
gcc-4.5.3.20110210. After some FreeBSD specific adaptions Dirk made some
weeks ago Rcpp works great now ;-)
Some more information for people who are interested in:
This is R-2.13.0 with sessionInfo()
R version 2.13.0 Under development (unstable) (2011-02-22 r54523)
Platform: x86_64-unknown-freebsd9.0 (64-bit)
locale:
[1] de_DE.ISO8859-15/de_DE.ISO8859-15/C/C/de_DE.ISO8859-15/de_DE.ISO8859-15
attached base packages:
[1] stats graphics grDevices utils datasets methods base
# R CMD check Rcpp_0.9.1.tar.gz
* using log directory '/usr/home/rhurlin/CRAN-R/Packages/Rcpp.Rcheck'
* using R version 2.13.0 Under development (unstable) (2011-02-22 r54523)
* using platform: x86_64-unknown-freebsd9.0 (64-bit)
* using session charset: ISO8859-1
* checking for file 'Rcpp/DESCRIPTION' ... OK
* this is package 'Rcpp' version '0.9.1'
* checking package name space information ... OK
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking for executable files ... OK
* checking whether package 'Rcpp' can be installed ... OK
* checking installed package size ... NOTE
installed size is 18.1Mb
sub-directories of 1Mb or more:
libs 2.2Mb
doc 2.0Mb
include 5.6Mb
lib 7.7Mb
* checking package directory ... OK
* checking for portable file names ... OK
* checking for sufficient/correct file permissions ... OK
* checking DESCRIPTION meta-information ... OK
* checking top-level files ... OK
* checking index information ... OK
* checking package subdirectories ... OK
* checking R files for non-ASCII characters ... OK
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... OK
* checking whether the package can be loaded with stated dependencies ... OK
* checking whether the package can be unloaded cleanly ... OK
* checking whether the name space can be loaded with stated dependencies
... OK
* checking whether the name space can be unloaded cleanly ... OK
* checking for unstated dependencies in R code ... OK
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... OK
* checking Rd files ... OK
* checking Rd metadata ... OK
* checking Rd cross-references ... OK
* checking for missing documentation entries ... OK
* checking for code/documentation mismatches ... OK
* checking Rd \usage sections ... OK
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking line endings in C/C++/Fortran sources/headers ... OK
* checking line endings in Makefiles ... OK
* checking for portable compilation flags in Makevars ... OK
* checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
* checking examples ... OK
* checking for unstated dependencies in tests ... OK
* checking tests ...
Running 'doRUnit.R' OK
* checking package vignettes in 'inst/doc' ... OK
* checking PDF version of manual ... OK
Thanks again,
Rainer
_______________________________________________
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
