Do you know where the `library(cgwtools)` call came from? It appears to
be the culprit.
I'd try (command line)
R --vanilla
for a minimal load, then update packages, etc. Then try the regular
load. If it still fails, go back to vanilla, and source your .Rprofile
with echo = TRUE to see w
On 7/22/23 4:42 PM, David Winsemius wrote:
And I forgot to ask what's in your .Rprofile file?
Nothing that ever caused trouble in the past, but FWIW, here it is:
setwd('~/Rgames')
#print('diagnostic: ~/.Rprofile ran')
#doubt this'l work... 'quartz' not recognized by startup sequence
#qu
And I forgot to ask what's in your .Rprofile file?
On 7/22/23 13:29, Carl Witthoft wrote:
Neither R.app Gui nor R from command line will work.
This is 4.3.1 , MacOS 13.4 on an x86 (and yes, that's the version I
installed).
Heres the error traceback from the command line:
*** caught s
On 7/22/23 13:29, Carl Witthoft wrote:
Neither R.app Gui nor R from command line will work.
This is 4.3.1 , MacOS 13.4 on an x86 (and yes, that's the version I
installed).
Heres the error traceback from the command line:
*** caught segfault ***
address 0x0, cause 'memory not mapped'
Tra
Neither R.app Gui nor R from command line will work.
This is 4.3.1 , MacOS 13.4 on an x86 (and yes, that's the version I
installed).
Heres the error traceback from the command line:
*** caught segfault ***
address 0x0, cause 'memory not mapped'
Traceback:
1: as.bigz(NA)
2: fun(libname, p
