Re: [Rd] CRAN check for package on Sparc Solaris

This issue is discussed in http://cran.r-project.org/doc/manuals/r-release/R-exts.html#Writing-portable-packages, to which he was referred by the CRAN report. It fails in the same way with --disable-long-double on an x86_64 Linux box (as he was told). On 13/05/2015 20:48, Viechtbauer Wolfgang

Re: [Rd] Reading exit code of pipe()

Hi Jeroen, I think `pipe` might just be returning the status code of the underlying command executed; for example, I get a status code of '0' when I test a pipe on `ls`: conn <- pipe("ls") stream <- readLines(conn) print(close(conn)) Similarly, I get an error code if I try to `ls` a

[Rd] Reading exit code of pipe()

Is there a way to get the status code of a pipe() command? The documentation suggests that it might be returned by close, however this does not seem to be the case. con <- pipe("cat /etc/passwd", "r") stream <- readLines(con, n = 10) err <- close(con) print(err) __

Re: [Rd] Unexpected failure when calling new() with unnamed arg and

Thanks Martin for looking into this. H. On 05/13/2015 03:57 AM, Martin Maechler wrote: Hervé Pagès on Tue, 12 May 2015 15:18:42 -0700 writes: Hi, The man page for new() suggests that if 'a' is an object with slots "slot1" and "slot2" and C is a class that extends the class of 'a', t

Re: [Rd] LDFLAGS defined in R_MAKEVARS_USER file is ignored for R CMD SHLIB on Windows

I have tracked this discrepancy down to the use of `SHLIB_LD` rather than `SHLIB_LINK` in share/make/winshlib.mk . This variable has been used in winshlib.mk since svn r47953

Re: [Rd] CRAN check for package on Sparc Solaris

Thank you for the kind offer! Unfortunately, the problem is really Sparc Solaris: http://cran.r-project.org/web/checks/check_results_metafor.html On Solaris x86 and all other flavors, it passes without errors. Best, Wolfgang From: Gábor Csárdi [csardi.ga...@gmail.com] Sent: Wednesday, May 13,

Re: [Rd] CRAN check for package on Sparc Solaris

Hi Wolfgang, I can test your package, please send it to me in private. Btw. I only have an x86 machine, and no sparc, so if your problem is sparc-specific, then my test is probably useless. Gabor On Wed, May 13, 2015 at 3:48 PM, Viechtbauer Wolfgang (STAT) < wolfgang.viechtba...@maastrichtuniver

[Rd] CRAN check for package on Sparc Solaris

Dear All, The metafor package currently fails CRAN checks on Sparc Solaris: http://cran.r-project.org/web/checks/check_results_metafor.html The problem is probably due to an unintended (= stupid) use of identical() in a couple tests. I have changed that to more appropriate tests using all.equal

Re: [Rd] example fails during R CMD CHECK but works interactively?

Thank you Dan but it isn't my tests that are failing (all of them pass without problem) but one of the examples from the inst/examples directory. I did try, however, to start R with the environmental variables as you suggest but it had no effect on my tests. Charles On Wed, May 13, 2015 at 1:51 P

Re: [Rd] example fails during R CMD CHECK but works interactively?

- Original Message - > From: "Charles Determan" > To: r-devel@r-project.org > Sent: Wednesday, May 13, 2015 11:31:36 AM > Subject: [Rd] example fails during R CMD CHECK but works interactively? > > Greetings, > > I am collaborating with developing the bigmemory package and have run > i

[Rd] example fails during R CMD CHECK but works interactively?

Greetings, I am collaborating with developing the bigmemory package and have run in to a strange problem when we run R CMD CHECK. For some reason that isn't clear to us one of the examples crashes stating: Error: memory could not be allocated for instance of type big.matrix You can see the out

Re: [Rd] Alternative for wildcard gnu extension in Makevars

While at it: 'Makevars' is an R invention (i.e. documentation of it is only available through the R docs), correct? /Henrik On Wed, May 13, 2015 at 10:10 AM, Kevin Ushey wrote: > One other solution that's only a little crazy: you could have a R > function within your package that generates the

Re: [Rd] Alternative for wildcard gnu extension in Makevars

On 13-05-15 18:08, Gábor Csárdi wrote: On Wed, May 13, 2015 at 12:05 PM, Jan van der Laan mailto:rh...@eoos.dds.nl>> wrote: [...] Too bad. Since it is only a handful of files, I will probably move them directly into the src directory and prefix them. It would have been nice to have

Re: [Rd] Alternative for wildcard gnu extension in Makevars

On 13 May 2015 at 10:10, Kevin Ushey wrote: | One other solution that's only a little crazy: you could have a R | function within your package that generates the appropriate (portable) | Makevars, and within the package `configure` script call that | function. For example" | | R --vanilla --s

Re: [Rd] Why is the diag function so slow (for extraction)?

> From: Martin Maechler > diag() should not work only for pure matrices, but for all > "matrix-like" objects for which ``the usual methods'' work, such > as >as.vector(.), c(.) > > That's why there has been the c(.) in there. > > You can always make code faster if you write the code so it o

Re: [Rd] Alternative for wildcard gnu extension in Makevars

One other solution that's only a little crazy: you could have a R function within your package that generates the appropriate (portable) Makevars, and within the package `configure` script call that function. For example" R --vanilla --slave -e "source('R/makevars.R'); makevars()" And that 'm

Re: [Rd] Why is the diag function so slow (for extraction)?

As kindly pointed out to me (oh my decaying gray matter), is.object() is better suited for this test; $ svn diff src/library/base/R/diag.R Index: src/library/base/R/diag.R === --- src/library/base/R/diag.R (revision 68345) +++ src/l

Re: [Rd] Alternative for wildcard gnu extension in Makevars

On Wed, May 13, 2015 at 12:05 PM, Jan van der Laan wrote: [...] > Too bad. Since it is only a handful of files, I will probably move them > directly into the src directory and prefix them. It would have been nice to > have been able to keep them separate. > If it is a couple of files, then you c

Re: [Rd] Alternative for wildcard gnu extension in Makevars

Dirk Eddelbuettel schreef: On 13 May 2015 at 17:27, Jan van der Laan wrote: | | I have some cpp-files from another library (boost) in a subdirectory | in my src directory (src/boost_src). I include these using the | following two lines in my Makevars: | | SOURCES = $(wildcard *.cpp boost_src/*

Re: [Rd] Alternative for wildcard gnu extension in Makevars

On 13 May 2015 at 17:27, Jan van der Laan wrote: | | I have some cpp-files from another library (boost) in a subdirectory | in my src directory (src/boost_src). I include these using the | following two lines in my Makevars: | | SOURCES = $(wildcard *.cpp boost_src/*.cpp) | OBJECTS = $(SOURC

[Rd] Alternative for wildcard gnu extension in Makevars

I have some cpp-files from another library (boost) in a subdirectory in my src directory (src/boost_src). I include these using the following two lines in my Makevars: SOURCES = $(wildcard *.cpp boost_src/*.cpp) OBJECTS = $(SOURCES:.cpp=.o) However, R CMD check complains about my use of 'w

Re: [Rd] Unexpected failure when calling new() with unnamed arg and

> Hervé Pagès > on Tue, 12 May 2015 15:18:42 -0700 writes: > Hi, > The man page for new() suggests that if 'a' is an object with slots > "slot1" and "slot2" and C is a class that extends the class of 'a', > then the 2 following calls should be equivalent: >new("C", a, ...) >