I am trying to cross compile R-2.6.0 for ARM. I have my cross compiling
tool chain set up already.
I've read the cross compiling guide for WIN
# http://cran.r-project.org/doc/contrib/cross-build.pdf
# http://cran.r-project.org/doc/contrib/Makefile-rcb
Following the same approach, I compiled the
On 06/12/2007, Marc Schwartz <[EMAIL PROTECTED]> wrote:
>
> On Thu, 2007-12-06 at 00:32 -0800, Deepayan Sarkar wrote:
> > On 12/6/07, Prof Brian Ripley <[EMAIL PROTECTED]> wrote:
> > > The defaults for postscript()
> > >
> > > paper = "default"
> > > onefile = TRUE
> > > horizontal = TRUE
> > >
> >
Gabor Grothendieck wrote:
>
> The closure only works if you are defining the inner function yourself.
> If you are not then its yet more work to redefine the environment of
> the inner function or other workaround.
>
> On Dec 6, 2007 6:01 PM, Peter Dalgaard <[EMAIL PROTECTED]> wrote:
>> Spence
Ben,
Thanks for the bug report. I am off two minds about it as discussed below.
But as it does indeed create a crash / segfault, I am passing this on to the
R bug tracker. A suggested two-line patch is below; I tested the patch
against a 'vanilla' 2.6.1 source tree.
On 6 December 2007 at 19:32,
The closure only works if you are defining the inner function yourself.
If you are not then its yet more work to redefine the environment of
the inner function or other workaround.
On Dec 6, 2007 6:01 PM, Peter Dalgaard <[EMAIL PROTECTED]> wrote:
> Spencer Graves wrote:
> > Hello:
> >
> > I
Spencer Graves wrote:
> Hello:
>
> I wish to again express my appreciation to all who have
> contributed to making R what it is today.
>
> At this moment, I'm particularly grateful for whoever modified the
> 'mle' code so data no longer need be passed via global variables. I
> rem
On Fri, 7 Dec 2007, Paul Murrell wrote:
> Hi
>
>
> Prof Brian Ripley wrote:
>> The defaults for postscript()
>>
>> paper = "default"
>> onefile = TRUE
>> horizontal = TRUE
>>
>> (it seems) date from the days when people used to used this to send plots
>> directly to a postscript printer via print.
As a quick follow up, this problem is apparent in the Postscript device
too (and possibly other vector devices).
For example:
dat <- data.frame(f=factor(rep(1:4, 10)), x=rnorm(40))
postscript("test.ps")
plot(dat)
dev.off()
In Adobe Illustrator, the compound path needs to be "released" to see
th
Full_Name: Michael Toews
Version: 2.61
OS: WinXP SP2
Submission from: (NULL) (142.58.206.114)
Using boxplot on a PDF device with more than one group (or boxes) produces
multiple (and overlain) 1st and 3rd quartile ticks. There are exactly the
multiple of boxplot groups as there are of each 1st an
On Dec 6, 2007, at 9:26 AM, Aaron Robotham wrote:
> I know of gdb but I'm not certain how to use it with Mac OS X's =20
> R.app, do you just do something like "gdb open R.app" in the =20
> terminal?.
>
You can attach it once it's running - just type "attach R" in gdb =20
while R is runningm then
On Dec 6, 2007, at 9:26 AM, Aaron Robotham wrote:
> I know of gdb but I'm not certain how to use it with Mac OS X's
> R.app, do you just do something like "gdb open R.app" in the
> terminal?.
>
You can attach it once it's running - just type "attach R" in gdb
while R is runningm then "c",
This is likely a result of RGtk2 "piggybacking" on the tcl/tk event loop on
Windows. One workaround in your situation is run gtkMain() at the R console
to force the GTK+ event loop to run. The downside is that the R console will
no longer be responsive. It's tough to keep so many interfaces workin
Full_Name: Hans Dieter
Version: 2.6.1
OS: windows
Submission from: (NULL) (217.93.91.19)
Hi all,
first I used a TCL/TK GUI, after my work I cloed it and opend an RGTK2 GUI.
Now I have the problem, the RGTK2 GUI will not refresh correctly and basic
user-commands ( close windows ) dosen't work.
Gr
I know of gdb but I'm not certain how to use it with Mac OS X's R.app,
do you just do something like "gdb open R.app" in the terminal?.
Interestingly I don't get this crash when I launch the X11 version of
R through the terminal, so this would suggest the bug in question is
to do with the actual R
Hi
Nicholas Lewin-Koh wrote:
> Hi,
> The move to sRGB is nice, is there any interest in adding an interface
> to lcms, http://www.littlecms.com,
> to allow gamut matching? I can think of a lot of instances where I would
> like to render a
> figure as it would appear on my printer. This is probabl
Hi
Prof Brian Ripley wrote:
> The defaults for postscript()
>
> paper = "default"
> onefile = TRUE
> horizontal = TRUE
>
> (it seems) date from the days when people used to used this to send plots
> directly to a postscript printer via print.it=TRUE. I haven't done that
> for years, and it s
On Dec 6, 2007, at 12:30 PM, [EMAIL PROTECTED] wrote:
>> I had seen old posts on the list (circa 2002) regarding a Cocoa-R
>> bridge that was under development, but I can't find anything recent
>> about it. Does anyone know if this is available somewhere? If not,
>> does anyone have any expe
Hello:
I wish to again express my appreciation to all who have
contributed to making R what it is today.
At this moment, I'm particularly grateful for whoever modified the
'mle' code so data no longer need be passed via global variables. I
remember struggling with this a couple
The problem is at least as old as 2.5.1. Looks like a line disappeared
from trace(), something like:
on.exit(tracingState(tState))
As a result, if an error occurs in the call to trace(), the tracing
state is left FALSE. The workaround is to turn it on explicitly:
tracingState(TRUE)
a
On Dec 6, 2007, at 11:58 AM, Lee Falin wrote:
> I had seen old posts on the list (circa 2002) regarding a Cocoa-R
> bridge that was under development, but I can't find anything recent
> about it. Does anyone know if this is available somewhere? If not,
> does anyone have any experience/po
> I had seen old posts on the list (circa 2002) regarding a Cocoa-R bridge
> that was under development, but I can't find anything recent about it.
> Does anyone know if this is available somewhere? If not, does anyone
> have any experience/pointers calling R functions from Cocoa?
The R build
I had seen old posts on the list (circa 2002) regarding a Cocoa-R
bridge that was under development, but I can't find anything recent
about it. Does anyone know if this is available somewhere? If not,
does anyone have any experience/pointers calling R functions from Cocoa?
Thanks for your ti
On Thu, 2007-12-06 at 00:32 -0800, Deepayan Sarkar wrote:
> On 12/6/07, Prof Brian Ripley <[EMAIL PROTECTED]> wrote:
> > The defaults for postscript()
> >
> > paper = "default"
> > onefile = TRUE
> > horizontal = TRUE
> >
> > (it seems) date from the days when people used to used this to send plot
G'day Serge,
On Thu, 6 Dec 2007 13:34:58 +0100
"de Gosson de Varennes Serge (4100)"
<[EMAIL PROTECTED]> wrote:
> I have a major problem (major for me that is) with solve.QP and I'm
> new at this. You see, to solve my quadratic program I need to have
> the lagrange multipliers after each iteration
trace() seems to be broken in 2.6.1 and R-devel:
Try the example from the ?debug man page:
> library(methods)
> trace("plot", browser, exit=browser, signature = c("track",
+ "missing"))
Error in getFunction(what, where = whereF) : no function "plot" found
Okay, it's just an example that
Hi there,
I have a major problem (major for me that is) with solve.QP and I'm new at
this. You see, to solve my quadratic program I need to have the lagrange
multipliers after each iteration. Solve.QP gives me the solution, the
unconstrained solution aswell as the optimal value. Does anybody ha
Hi,
The move to sRGB is nice, is there any interest in adding an interface
to lcms, http://www.littlecms.com,
to allow gamut matching? I can think of a lot of instances where I would
like to render a
figure as it would appear on my printer. This is probably best done as a
separate package though,
a
On 12/6/07, Prof Brian Ripley <[EMAIL PROTECTED]> wrote:
> The defaults for postscript()
>
> paper = "default"
> onefile = TRUE
> horizontal = TRUE
>
> (it seems) date from the days when people used to used this to send plots
> directly to a postscript printer via print.it=TRUE. I haven't done tha
The defaults for postscript()
paper = "default"
onefile = TRUE
horizontal = TRUE
(it seems) date from the days when people used to used this to send plots
directly to a postscript printer via print.it=TRUE. I haven't done that
for years, and it seems that our current generation of students don
29 matches
Mail list logo
