Thank you, William and Berend, for your thorough replies. I have still the
habit of setting "long int" variables because, when I first learnt C, the
manual said that "int" could be up to around 3.2e4. But I suppose that, in
systems from 32 bits, an "int" number can be much larger, isn't it?
- whic
- which version of Mac OS X?
- Which version of R? (version, architecture)
- Officially provided R or compiled by you? Official R is compiled with
Apple gcc.
- if R was compiled with Apple compiler, who knows what can happen if you
link with code compiled with a non Apple gcc?
- if the code runs o
unlap tibco.com
From: David [mailto:david.mailli...@gmail.com]
Sent: Wednesday, October 13, 2010 11:13 AM
To: William Dunlap
Cc: r-help@r-project.org
Subject: Re: [R] "Memory not mapped" when using .C,proble
ge-
> > From: r-help-boun...@r-project.org
> > [mailto:r-help-boun...@r-project.org] On Behalf Of David
> > Sent: Wednesday, October 13, 2010 6:47 AM
> > To: r-help@r-project.org
> > Subject: [R] "Memory not mapped" when using .C,problem in Mac
> > but
n Behalf Of David
> Sent: Wednesday, October 13, 2010 6:47 AM
> To: r-help@r-project.org
> Subject: [R] "Memory not mapped" when using .C,problem in Mac
> but not in Linux
>
> Hello,
>
> I am aware this may be an obscure problem difficult to advice
> about, but
Hello,
I am aware this may be an obscure problem difficult to advice about, but
just in case... I am calling a C function from R on an iMac (almost shining:
bought by my institution this year) and gives a "memory not mapped" error.
Nevertheless, exactly the same code runs without problem in a pow
6 matches
Mail list logo