> On 23 Nov 2015, at 11:50, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > > The OSX binary version of rgl on CRAN is ancient. You'll need to reinstall it from source for a current one.Since you bring up this point: any chance of getting Mac binaries from CRAN again? Rgl is a particularly nice tool because of its portability, and requiring users to install Xcode and Xquartz first makes life a lot harder for non-technical users. This is compounded by the fact that the automatic configuration is easily broken. I have been unable to install rgl from source for some time on Mavericks, and have now discovered that this was due to a HomeBrew-installed imake in /usr/local. Perhaps it would make sense always to use the well-known standard XQuartz paths on Mac and only consider other locations if explicitly asked for by the user? Best, Stefan
On 23/11/2015 7:45 AM, Stefan Evert wrote:> >> On 23 Nov 2015, at 11:50, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: >> >> The OSX binary version of rgl on CRAN is ancient. You'll need to reinstall it from source for a current one. > > Since you bring up this point: any chance of getting Mac binaries from CRAN again?You would have to ask them. I don't know why they aren't building it. Duncan Murdoch Rgl is a particularly nice tool because of its portability, and requiring users to install Xcode and Xquartz first makes life a lot harder for non-technical users.> > This is compounded by the fact that the automatic configuration is easily broken. I have been unable to install rgl from source for some time on Mavericks, and have now discovered that this was due to a HomeBrew-installed imake in /usr/local. > > Perhaps it would make sense always to use the well-known standard XQuartz paths on Mac and only consider other locations if explicitly asked for by the user? > > Best, > Stefan > ______________________________________________ > R-help at r-project.org mailing list -- To UNSUBSCRIBE and more, see > https://stat.ethz.ch/mailman/listinfo/r-help > PLEASE do read the posting guide http://www.R-project.org/posting-guide.html > and provide commented, minimal, self-contained, reproducible code. >
Some comments on the second part of your message. On 23/11/2015 7:45 AM, Stefan Evert wrote:> >> On 23 Nov 2015, at 11:50, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: >> >> The OSX binary version of rgl on CRAN is ancient. You'll need to reinstall it from source for a current one. > > Since you bring up this point: any chance of getting Mac binaries from CRAN again? Rgl is a particularly nice tool because of its portability, and requiring users to install Xcode and Xquartz first makes life a lot harder for non-technical users. > > This is compounded by the fact that the automatic configuration is easily broken. I have been unable to install rgl from source for some time on Mavericks, and have now discovered that this was due to a HomeBrew-installed imake in /usr/local. > > Perhaps it would make sense always to use the well-known standard XQuartz paths on Mac and only consider other locations if explicitly asked for by the user?If rgl is using non-standard features in its makefiles, let me know what they are. I use GNU make, so it's easy for GNUisms to slip into it. We already have special handling for X11 on the Mac. I don't know why yours isn't working, but it's pretty well-known that homebrew breaks the usual R build system, so I'd blame it on that. If you are using homebrew, you should be prepared to manually configure rgl. Or you can send me a patch to rgl's configure.ac that works around the differences, and I'll try it out. Duncan Murdoch
> On 24 Nov 2015, at 13:32, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > >> Perhaps it would make sense always to use the well-known standard XQuartz paths on Mac and only consider other locations if explicitly asked for by the user? > > If rgl is using non-standard features in its makefiles, let me know what they are. I use GNU make, so it's easy for GNUisms to slip into it.I didn't have any problems with GNUisms ? I only use GNU make anyway.> We already have special handling for X11 on the Mac. I don't know why yours isn't working, but it's pretty well-known that homebrew breaks the usual R build system, so I'd blame it on that.Yes, it turned out that I had a bogus xmkmf in /usr/local/bin, which I had inadvertently installed through homebrew. My fault.> If you are using homebrew, you should be prepared to manually configure rgl. Or you can send me a patch to rgl's configure.ac that works around the differences, and I'll try it out.My thought was to prefer the known standard location of XQuartz to any automatically discovered X11 configuration on Darwin, i.e. run a test for X headers and libs in this location first, before trying xmkmf. I guess that normally someone who has xmkmf would want to use this configuration rather than the standard one, so let's quietly forget about this idea. In case anybody else encounters a similar problem ? no X11 found even they know they've installed XQuartz ? the first thing you should do is to check "which xmkmf". If you find one, it is likely to be the cause of the failure. Best, Stefan