Re: [R-pkg-devel] Catching console messages from libGL

2020-02-18 Thread Duncan Murdoch
On 17/02/2020 4:10 p.m., Ivan Krylov wrote: On Mon, 17 Feb 2020 14:56:31 -0500 Duncan Murdoch wrote: So how do I capture stderr (or, off topic here, how do I get libGL to be quiet)? libGL seems to only offer bad news in this regard: it writes directly to stderr [1] and does not seem to

Re: [R-pkg-devel] Catching console messages from libGL

2020-02-17 Thread Ivan Krylov
On Mon, 17 Feb 2020 14:56:31 -0500 Duncan Murdoch wrote: > So how do I capture stderr (or, off topic here, how do I get libGL to > be quiet)? libGL seems to only offer bad news in this regard: it writes directly to stderr [1] and does not seem to offer a way to silence the _LOADER_FATAL

Re: [R-pkg-devel] Catching console messages from libGL

2020-02-17 Thread Duncan Murdoch
On 17/02/2020 2:56 p.m., Duncan Murdoch wrote: I'm working on the initialization code for rgl, especially for the case when it is running remotely and the user is connecting using X11. On some machines, this fails: I now understand that's because the local machine needs to enable "indirect

[R-pkg-devel] Catching console messages from libGL

2020-02-17 Thread Duncan Murdoch
I'm working on the initialization code for rgl, especially for the case when it is running remotely and the user is connecting using X11. On some machines, this fails: I now understand that's because the local machine needs to enable "indirect GLX" (IGLX) for it to succeed, and by default