Thanks a lot for the answer!
I unfortunately wasn’t able to reproduce it with the same OS + compiler
+ valgrind settings, but from what I see in the message, turns out in
the end it might indeed be due to Cereal copying raw bytes into an R
vector and Valgrind complaining about the copied bytes rat
If you don't mind multi-gig docker containers, this can be helpful:
https://github.com/scottyhardy/docker-wine
It doesn't work with 64 bit versions of R as far as I could tell, but 32
bit did install and start correctly in a few clicks when I tried last year.
On Wed, Jul 15, 2020 at 10:56 AM
Are you sure you want to try to run R etc. under Wine?
- If you have Windows running, either directly or in a VM, you can run R there.
- If you have Windows and want to run R under some other OS, then set up a VM
e.g., Linux Mint, for that. I sometimes test R for Windows in a VirtualBox VM
for Win
Does anyone know of a setup guide for getting R and Rtools 4.0 up and
running on Wine with the Windows Server 2008 R2 VM? Do other maintainers
with more knowhow think that would be useful for debugging purposes?
I've been trying to test out some flto gcc things for windows by setting up
a local wi
On Wed, 08 Jul 2020 22:43:13 +0300
David Cortes wrote:
> About the source code: it actually complains about line
> fit_model.cpp:751 :
> hplane_root->reserve(exp_nodes);
My fault. I was reading the GitHub source code instead of CRAN package
source code.
> I’m not able to reproduce the warning w
