Thank you very much, Simon, for your information and your work.
Although the message below was not referencing the problem I had, it has been
very useful for me.
The Mac R GUI: "R-GUI-7903-4.0-high-sierra-Debug" works fine now.
My problem with the R GUI (with a 16-inch MacBook Pro 2019, Big Sur
> On 14 Dec 2020, at 23:07 , John Helly via R-SIG-Mac
> wrote:
>
> Aloha.
>
> Don't know if this is uniquely a Mac issue or not. I will try to test on a
> Linux distro later today. \\\
>
> In the meantime, here's the additional info. Thanks for the responses. I
> created a test
Hello all:
My apologies if I’m not providing this information in a useful manner, I’m new
to this list. I’d be happy to revise this message for greater clarity with a
little advice from the list. After upgrading to Big Sur on a 16 inch Macbook
Pro, I’ve noticed an NSButton warning message.
Unfortunately, I don't have a Mac with a touch bar to replicate it, I'll see if
there is any other way to test it. The GUI doesn't actually use the touch bar,
so it's not clear where that message comes from. It seems like just a benign
output from the system - it doesn't really affect any
I don't think that is feasible (assuming you mean macOS 11 arm64 system running
in a VM). Note that M1 is not just the CPU, there is much tighter integration
of all the components so you'd have to emulate a lot more than that and also
all the Apple security components etc. in order to be able
To my best knowledge the only way to test anything on M1 is to buy one. As far
as I know there is no virtual solution yet. If you see one, let me know.
As for CRAN there is no official arm64 build yet - the hardware just arrived
and I need to setup the nightly builds first before moving to
Something like https://wiki.debian.org/Arm64Qemu ?
___
R-SIG-Mac mailing list
R-SIG-Mac@r-project.org
https://stat.ethz.ch/mailman/listinfo/r-sig-mac
On Tue, Dec 15, 2020 at 03:54:12PM +1300, Simon Urbanek wrote:
> I don't think that is feasible (assuming you mean macOS 11 arm64
> system running in a VM). Note that M1 is not just the CPU, there is
> much tighter integration of all the components so you'd have to
> emulate a lot more than
Simon, many thanks for your response. The only real danger in leaving it there
is that the big red error message will frighten a newbie who will think they
have done something very bad!
Peter
> On Dec 14, 2020, at 9:43 PM, Simon Urbanek
> wrote:
>
> Unfortunately, I don't have a Mac with a
We discussed this in r-sig-mac a couple of weeks ago but the thread got hijacked by unrelated Big Sur issues and I don’t think this problem was ever resolved.
It seems to be an issue with R GUI and MacBook Pro. It arose with the final versions of Catalina and continued with Big Sur on
I’m sorry I missed the earlier discussion; I only joined this mailing list on
Dec 12. For what it’s worth, I recall observing the same problem on a 15 inch
Macbook Pro running Catalina, that I no longer own. However, there were other
problems of my own making with that particular machine, so I
Aloha.
Don't know if this is uniquely a Mac issue or not. I will try to test
on a Linux distro later today. \\\
In the meantime, here's the additional info. Thanks for the responses.
I created a test subset of the input data so it is just the first DAUCO
value subset (i.e., 00125).
In
12 matches
Mail list logo
