search for: quarendon

...t you are saying is that there's a file called Makeconf in the etc directory under the R_HOME that contains the information. That certainly seems to be true for Linux. Thanks. -----Original Message----- From: G?bor Cs?rdi [mailto:csardi.gabor at gmail.com] Sent: 22 January 2016 11:37 To: Tom Quarendon <tom.quarendon at teamwpc.co.uk> Cc: r-devel at r-project.org Subject: Re: [Rd] Return options used to configure R A one liner that should work on most systems: grep("configure", readLines(file.path(R.home(), "etc", "Makeconf")), value=TRUE) Gabor On Thu, Jan...

...info. The Makeconf file is what I want. At least on Linux, doesn't appear to exist on our OSX installation, but we probably installed that from a pre-built package. Ditto Windows. -----Original Message----- From: Dirk Eddelbuettel [mailto:edd at debian.org] Sent: 22 January 2016 12:07 To: Tom Quarendon <tom.quarendon at teamwpc.co.uk> Cc: G?bor Cs?rdi <csardi.gabor at gmail.com>; r-devel at r-project.org Subject: Re: [Rd] Return options used to configure R On 22 January 2016 at 11:40, Tom Quarendon wrote: | So in English what you are saying is that there's a file called Makeconf...

Is there any way to print out the options that where passed to configure when R was built? I want to build a later version to the one I have on my machine, and I want to build it in the same way, with the same configure options. Thanks.

On Tue, 12 Aug 2008, Chris Lattner wrote: > > On Aug 12, 2008, at 10:55 AM, Tom Tromey wrote: > >>>>>>> "Tom" == Tom Quarendon <tom at quarendon.net> writes: >> >> Tom> I imagine that GCJ has do to this ind of thing? >> >> FWIW, libgcj does not include a JIT compiler. >> So, no solution there, sorry. > > It's OT for this list, but the LLVM JIT can generate DWARF EH informa...

...GCC uses, but so far I can't see the whole picture in terms of what I'd actually do with those tables in terms of registering them with the exception handler. I was hoping that I could mock up something similar using LLVM to see what it did. Any help on this would be great thanks. Tom Quarendon. ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________

I have a general question about R's usage or memory and what limits exist on the size of datasets it can deal with. My understanding was that all object in a session are held in memory. This implies that you're limited in the size of datasets that you can process by the amount of memory you've got access to (be it physical or paging). Is this true? Or does R store objects on disk

Possibly more of a legal question than a technical development question, but here goes. In the doc\COPYRIGHTS file it is made clear that the intention is that you can write R packages and distribute them under licenses not compatible with GPL, by making the relevant header files available under the LGPL. This was an explicit change that was made in February 2001, and allows for DLLs that

Note I'm not asking for any legal advice here obviously, simply what the intention of the R foundation is with regard to allowing commercial connection to R. I've looked at various threads on the r-devel archive and it looks like this may have been discussed before, but as far as could tell, not to any great resolution, and not, it seems, specifically covering this angle. In the