On 2015-11-23 23:43, peter dalgaard wrote:
On 23 Nov 2015, at 22:30 , aixtools wrote:
./configure --enable-maintainer-mode ...
Two things here
- possibly irrelevant, but I'd avoid building in the source directory. (mkdir
../BUILD ; cd ../BUILD; ../R/configure)
I'll try this. It is a requir
On 2015-11-23 23:33, Paul Grosu wrote:
Hi Michael,
I experienced the same thing in the past. After you get the R-3.2.2.tar.gz
and uncompress it, enter the R-3.2.2 directory and run the ./configure and
make from there, rather than a different one.
I have been able to get a 32-bit build, easily,
On 2015-11-23 23:43, peter dalgaard wrote:
On 23 Nov 2015, at 22:30 , aixtools wrote:
./configure --enable-maintainer-mode ...
Two things here
- possibly irrelevant, but I'd avoid building in the source directory. (mkdir
../BUILD ; cd ../BUILD; ../R/configure)
- don't turn on mantainer mod
Jeroen,
I agree that it may be useful to have some kind of "finally"-like
infrastructure. However, in the use cases you list there are already ways to do
that - the same way that R_alloc uses. First, you don't need to call UNPROTECT
- the whole point is that the protection stack is automaticall
On Mon, Nov 23, 2015 at 11:39 AM, David Smith wrote:
> Hi Paul,
>
> We've been through this process ourselves for the Revolution R Open project.
> There are a number of pitfalls to avoid, but you can take a look at how we
> achieved it in the build scripts at:
>
> https://github.com/RevolutionAn
