[Rd] can't use ATLAS or ACML | 2.9.0

So, tried again from scratch. Again, CentOS 5.3, which is essentially RHEL 5.3. ./configure --with-blas=-L/opt/acml4.3.0/gfortran64/lib -lacml In config.log, get things like configure:37199: checking for dgemm_ in -L/opt/acml4.3.0/gfortran64/lib -lacml configure:37230: gcc -std=gnu99 -o

Re: [Rd] Rd: pdf manual: package information not on first page

Duncan Murdoch schrieb: So my question is, if there is any possibility to get the package documentation on the first page? That's where it is supposed to be. Could you look for errors in the one where it comes last? If you can't spot anything, you could send me the tar.gz version of it and

Re: [Rd] Rd: pdf manual: package information not on first page

Thorn Thaler wrote: Duncan Murdoch schrieb: So my question is, if there is any possibility to get the package documentation on the first page? That's where it is supposed to be. Could you look for errors in the one where it comes last? If you can't spot anything, you could send me

Re: [Rd] Rd: pdf manual: package information not on first page

Duncan Murdoch schrieb: How did you produce the manual? When I do R CMD Rd2dvi on a package, I get the package man page first. There are other ways to produce the manual, and in some cases we may not control the sort order. Well, I see. There is a misunderstanding regarding the term package

Re: [Rd] Problem making the manuals (make dvi and make pdf)

Hi Roland, On 26 June 2009 at 10:46, Rau, Roland wrote: | Dear all, | | I am trying to compile and install R from sources on Ubuntu GNU/Linux 64 | bit. It usually worked flawlessly for me for more than 4 years (32bit | and 64bit on Mandrake/Mandriva, Suse, Debian, Ubuntu). However, I am |

Re: [Rd] Problem making the manuals (make dvi and make pdf)

Dear Dirk, thank you very much! -Original Message- From: Dirk Eddelbuettel [mailto:e...@debian.org] Sent: Friday, June 26, 2009 1:55 PM To: Rau, Roland Cc: r-devel@r-project.org Subject: Re: [Rd] Problem making the manuals (make dvi and make pdf) Hi Roland, On 26 June

Re: [Rd] Rd: pdf manual: package information not on first page

On 26/06/2009 7:36 AM, Thorn Thaler wrote: Duncan Murdoch schrieb: How did you produce the manual? When I do R CMD Rd2dvi on a package, I get the package man page first. There are other ways to produce the manual, and in some cases we may not control the sort order. Well, I see. There is a

Re: [Rd] can't use ATLAS or ACML | 2.9.0

On Fri, 26 Jun 2009, Evan Cooch wrote: So, tried again from scratch. Again, CentOS 5.3, which is essentially RHEL 5.3. ./configure --with-blas=-L/opt/acml4.3.0/gfortran64/lib -lacml In config.log, get things like configure:37199: checking for dgemm_ in -L/opt/acml4.3.0/gfortran64/lib

Re: [Rd] can't use ATLAS or ACML | 2.9.0

Brian - Cheers - followups below. Prof Brian Ripley wrote: On Fri, 26 Jun 2009, Evan Cooch wrote: So, tried again from scratch. Again, CentOS 5.3, which is essentially RHEL 5.3. ./configure --with-blas=-L/opt/acml4.3.0/gfortran64/lib -lacml In config.log, get things like configure:37199:

Re: [Rd] R data inspection under gdb?

Thanks, that was very helpful! Kynn On Thu, Jun 25, 2009 at 6:05 PM, Martin Morgan mtmor...@fhcrc.org wrote: Hi Kynn -- (gdb) call Rf_PrintValue(x) 'void' is I think the return value of R_PV() Martin Kynn Jones wrote: Hi, everyone. I'm trying to debug an R-module, written in C, and

[Rd] bug in Rf_PrintValue ?

I'm very green with R, so maybe this is not a bug, but it looks like one to me. The following program segfaults at the second call to Rf_PrintValue(). To failure depends on the value of the y-string. E.g., if I change it from coverage to, say, COVERAGE, the segfault does not occur. /* bug.c */

[Rd] beginner's guide to C++ programming with R packages?

Hello, again. I'm interested to learn how programmers develop test C/C++ code with R packages in Linux. I've been reading R source and the manual on Writing R Extensions but there are just a couple of details I can't understand. I wish I could watch over a developer's shoulder to see how

Re: [Rd] beginner's guide to C++ programming with R packages?

If your just looking to build and test a single function written in C/C ++ you can try: R CMD SHLIB my.c Which will produce a object that can be loaded in R with 'dyn.load'. A simple R script including dyn.load('my.so') with your basic tests can then be run with: R --vanilla my.R HTH

[Rd] Bugs in unique of data.frame and matrix

R version 2.8.1 (2008-12-22) / Windows XP There are several bugs in unique for data frames and matrices. Please find minimal reproducible examples below. -s -A- Unique of a vector uses numerical comparison: nn - ((1+2^-52)^(5:22)) unique(nn) [1] 1 1 1 1 1 1 1 1 1 1 1 1 1

Re: [Rd] bug in Rf_PrintValue ?

Kynn Jones wrote: I'm very green with R, so maybe this is not a bug, but it looks like one to me. The following program segfaults at the second call to Rf_PrintValue(). To failure depends on the value of the y-string. E.g., if I change it from coverage to, say, COVERAGE, the segfault does

[Rd] should Sys.glob() cope with a UNC windows path beginning with backslashes?

I find that Sys.glob() doesn't like UNC paths where the initial slashes are backslashes. The help page for Sys.glob() doesn't specificly mention UNC paths, but does say: File paths in Windows are interpreted with separator \ or /. Is the failure to treat a path beginning with a

Re: [Rd] should Sys.glob() cope with a UNC windows path beginning with backslashes?

On Fri, 26 Jun 2009, Tony Plate wrote: I find that Sys.glob() doesn't like UNC paths where the initial slashes are backslashes. The help page for Sys.glob() doesn't specificly mention UNC paths, but does say: File paths in Windows are interpreted with separator \ or /. Is the failure to