Well, my original report didn't give full information because R locked up too
early.
>From here I am following instructions and reporting back:
R version 4.0.4 RC (2021-02-12 r79998) -- "Lost Library Book"
Copyright (C) 2021 The R Foundation for Statistical Computing
Platform:
On 13/02/2021 5:43 p.m., Simon Urbanek wrote:
Duncan,
not really - this is why the XQuartz betas are such a disaster - they replace
libraries with incompatible versions (under same file name) - and even remove
some libraries, thus breaking anything that was compiled against either
version.
Duncan,
not really - this is why the XQuartz betas are such a disaster - they replace
libraries with incompatible versions (under same file name) - and even remove
some libraries, thus breaking anything that was compiled against either
version. If you downgrade, you have to re-compile anything
Richard,
thanks - finally a more complete output to go on. This is exactly the reminder
why it is so important to post the _full_output - the actual facts were
completely missing from your previous report.
Firstly, the xcrun output is just a warning which indicates that R can't find
out
On 13/02/2021 4:54 p.m., Simon Urbanek wrote:
As mentioned earlier, the issue is likely that your X11-auto-launch is not working. You
can start X11 (=XQuartz) yourself and set DISPLAY=:0 as you would on any unix system or
start X11 with X11(":0")
[personally, I hate that auto-launch "feature"
another fresh R session
> X11(":0")
xcrun: error: invalid active developer path
(/Library/Developer/CommandLineTools), missing xcrun at:
/Library/Developer/CommandLineTools/usr/bin/xcrun
Error in .External2(C_X11, d$display, d$width, d$height, d$pointsize, :
unable to start device X11
In
As mentioned earlier, the issue is likely that your X11-auto-launch is not
working. You can start X11 (=XQuartz) yourself and set DISPLAY=:0 as you would
on any unix system or start X11 with X11(":0")
[personally, I hate that auto-launch "feature" since it tries to start XQuartz
even if you
Have you tried the change to DISPLAY, i.e.
Sys.setenv(DISPLAY=":0.0")
before running X11()?
Duncan Murdoch
On 13/02/2021 3:50 p.m., Richard M. Heiberger wrote:
I tried this. It made no difference. Both before and after running
sudo xcode-select —install
I ran (in both cases, in a brand new
I tried this. It made no difference. Both before and after running
sudo xcode-select —install
I ran (in both cases, in a brand new *R* sessio n)
> X11()
xcrun: error: invalid active developer path
(/Library/Developer/CommandLineTools), missing xcrun at:
