Hi Mark,
Try pacman -Suy first to update pacman's package database. It's quite possible
that the versions pacman is trying to install are no longer available due to
being out of date.
HTH,
Cesko
-Original Message-
From: R-devel On Behalf Of Bravington, Mark
(Data61, Hobart)
Sent: Thu
I've not been able to install gdb for RTOOLS40 on Windows 10. The rtools
installer (rtools40-x64_86.exe) doesn't seem to include gdb by default, and
when I follow the instructions for adding gdb (which I tracked down at
https://github.com/r-windows/docs/blob/master/faq.md) this is what happened:
That would work.
Sys.info()['release']
# release
# "5.4.72-microsoft-standard-WSL2"
Brenton
From: Martin Maechler
Sent: Wednesday, April 14, 2021 03:28
To: Brenton Wiernik
Cc: r-devel@r-project.org
Subject: Re: [Rd] Sys.timezone() fails on Linux under Microsoft WSL
>>
On Fri, 26 Mar 2021 14:49:56 +0100
Martin Maechler wrote:
> I concluded I liked the first [patch] because it would achieve
> what's considered "uniformly better" in the sense that it makes
> R graphics behave like "all other" desktop applications *and* it
> would do so for all possible window m
Andreas,
What does any of this to do with CRAN? This not a the CRAN list - we're
discussing the proper approach of using valgrind and R can only assume that the
memory is uninitialised (since it cannot safely assume anything else) so it is
up to you to declare the memory as initialised if you
Andres,
correct me if I'm wrong, but the issue here is not initialisation but rather
valgrind flagging. You simply have to call VALGRIND_MAKE_MEM_DEFINED() in your
code after allocVector3() to declare that you have initialised the memory - or
am I missing something?
Cheers,
Simon
> On 30/
> Brenton Wiernik
> on Tue, 13 Apr 2021 09:15:50 -0400 writes:
> In Microsoft’s Windows Subsystem for Linux (WSL or WSL2),
> there is not system framework, so utilities that depend on
> it fail. This includes timedatectl which R uses in
> Sys.timezone(). The timedatect
