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 you compiled against the beta. That is probably one of the lesser evils since you can't expect anything to be forwards-compatible.
In theory, you could detect the version using otool - that's what X11() is doing to find whether XQuartz is present, but it only works for users that have dev tools installed, so not a good idea in general. Cheers, Simon > On Feb 14, 2021, at 11:32 AM, Duncan Murdoch <murdoch.dun...@gmail.com> wrote: > > 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" since it tries to start >> XQuartz even if you don't want it]. > > Thanks. Here's another datum: I did my last build of rgl with the beta > XQuartz installed. I'm now back to 2.7.11 and I get this when I try to start > rgl: > > > library(rgl) > Error in dyn.load(dynlib) : > unable to load shared object > '/Library/Frameworks/R.framework/Versions/4.0/Resources/library/rgl/libs/rgl.so': > dlopen(/Library/Frameworks/R.framework/Versions/4.0/Resources/library/rgl/libs/rgl.so, > 6): Library not loaded: /opt/X11/lib/libX11.6.dylib > Referenced from: > /Library/Frameworks/R.framework/Versions/4.0/Resources/library/rgl/libs/rgl.so > Reason: Incompatible library version: rgl.so requires version 11.0.0 or > later, but libX11.6.dylib provides version 10.0.0 > Error: package or namespace load failed for ‘rgl’: > .onLoad failed in loadNamespace() for 'rgl', details: > call: NULL > error: Loading rgl's DLL failed. > This build of rgl depends on XQuartz, which you can download from > xquartz.org. > > So it appears they updated the version of libX11.6.dylib, and rgl is asking > for the wrong one. > > Is there some way for me to request a particular version during my build, or > at least detect that the wrong version is installed? > > Duncan Murdoch > >> Cheers, >> Simon >>> On Feb 14, 2021, at 9:50 AM, Richard M. Heiberger <r...@temple.edu> 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 *R* sessio n) >>> >>>> X11() >>> xcrun: error: invalid active developer path >>> (/Library/Developer/CommandLineTools), missing xcrun at: >>> /Library/Developer/CommandLineTools/usr/bin/xcrun >>> >>> >>> My prior was that the xcode call was irrelevant is that X11() using XQuart >>> 8.0.3beta >>> worked with intel R_4.0.3 on the Mac M1. >>> >>> ________________________________________ >>> From: Dr Eberhard W Lisse <e...@lisse.na> >>> Sent: Saturday, February 13, 2021 3:33 AM >>> To: Simon Urbanek; R-SIG-Mac; Richard M. Heiberger >>> Cc: e...@lisse.na >>> Subject: [External] Re: [R-SIG-Mac] [External] Please test R 4.0.4 RC >>> >>> that has nothing to do with Xquartz but means you need to install the >>> Command line tools >>> >>> sudo xcode-select —install >>> >>> — >>> Sent from Dr Lisse’s iPhone >>> On 13 Feb 2021, 06:13 +0200, Richard M. Heiberger <r...@temple.edu>, wrote: >>> Using the intel R_4.0.4RC on the Mac M1. >>> >>> Based on your recommendation I reinstalled XQuartz 2.7.11 instead of the >>> 8.0.3beta. >>> X11() now does not work at all. >>> >>> X11() >>> xcrun: error: invalid active developer path >>> (/Library/Developer/CommandLineTools), missing xcrun at: >>> /Library/Developer/CommandLineTools/usr/bin/xcrun >>> C-c C-c C-c C-c >>> >>> Force-Killing XQuartz from the Activity Monitor doesn't help. >>> I have to Force-kill the R process. >>> >>> ________________________________________ >>> From: R-SIG-Mac <r-sig-mac-boun...@r-project.org> on behalf of Simon >>> Urbanek <simon.urba...@r-project.org> >>> Sent: Friday, February 12, 2021 6:50 PM >>> To: R-SIG-Mac >>> Subject: [External] [R-SIG-Mac] Please test R 4.0.4 RC >>> >>> Dear macOS useRs, >>> >>> please test the latest R 4.0.4 RC builds from >>> >>> https://mac.r-project.org/ >>> >>> especially if you are running macOS Big Sur. The known issues introduced by >>> Big Sur have been fixed, but I cannot replicate nor test the spurious >>> touchbar warning. >>> >>> Also a reminder to *not* install XQuartz betas even if XQuartz ask you to - >>> they are betas for a reason (=unstable) and break things. >>> >>> Cheers, >>> Simon >>> >>> _______________________________________________ >>> R-SIG-Mac mailing list >>> R-SIG-Mac@r-project.org >>> https://stat.ethz.ch/mailman/listinfo/r-sig-mac >>> >>> _______________________________________________ >>> R-SIG-Mac mailing list >>> R-SIG-Mac@r-project.org >>> https://stat.ethz.ch/mailman/listinfo/r-sig-mac >>> >> _______________________________________________ >> R-SIG-Mac mailing list >> R-SIG-Mac@r-project.org >> https://stat.ethz.ch/mailman/listinfo/r-sig-mac >> > > _______________________________________________ > R-SIG-Mac mailing list > R-SIG-Mac@r-project.org > https://stat.ethz.ch/mailman/listinfo/r-sig-mac _______________________________________________ R-SIG-Mac mailing list R-SIG-Mac@r-project.org https://stat.ethz.ch/mailman/listinfo/r-sig-mac