From: Harald Hanche-O. <ha...@ma...> - 2009-03-11 07:48:00
|
Is there a trick to making clx work with sbcl on macosx? It's been a year since last time I tried, and at the time it worked. Now it doesn't anymore: (xlib:open-display "unix") results in Connection failure to X11.0 server unix display 0: No protocol specified [Condition of type xlib:connection-failure] Same result with "" or "localhost" as the host part. Adding :protocol :tcp doesn't help, nor did I expect it to since the sbcl version of x-open-stream ignores the protocol argument. And yes, the X server is present on both localhost:0 and unix:0. What am I missing? This is sbcl 1.0.24.46 on osx 10.5.6/ppc (x11 2.3.2), clx 0.7.3. - Harald |
From: Robert G. <rpg...@si...> - 2009-03-11 13:14:50
|
Harald Hanche-Olsen wrote: > Is there a trick to making clx work with sbcl on macosx? > > It's been a year since last time I tried, and at the time it > worked. Now it doesn't anymore: > > (xlib:open-display "unix") results in > > Connection failure to X11.0 server unix display 0: No protocol specified > > [Condition of type xlib:connection-failure] > > Same result with "" or "localhost" as the host part. > Adding :protocol :tcp doesn't help, nor did I expect it to since the > sbcl version of x-open-stream ignores the protocol argument. > And yes, the X server is present on both localhost:0 and unix:0. > > What am I missing? This is sbcl 1.0.24.46 on osx 10.5.6/ppc (x11 > 2.3.2), clx 0.7.3. > I'm afraid I can't provide a complete answer, but I have a hazy recollection of something like this going wrong with me on ACL. My memory is that it occurred because OSX uses its launchd to start X, and there was a little fussing I needed to do to get the open display requests to trigger launchd properly to get X going. I submitted a patch which Mikel Bancroft considerably improved and put in his ACL fork of Christophe's CLX. I am not sure what would have happened after that because I don't know whether Mikel passed on this patch. Looks like Franz's darcs repo is at http://opensource.franz.com/clx/ I'm afraid I'm too inept with darcs to do any more than suggest that you just rummage around in the repository. best, r |
From: Harald Hanche-O. <ha...@ma...> - 2009-03-11 13:56:26
|
+ Robert Goldman <rpg...@si...>: > I'm afraid I can't provide a complete answer, but I have a hazy > recollection of something like this going wrong with me on ACL. My > memory is that it occurred because OSX uses its launchd to start X, and > there was a little fussing I needed to do to get the open display > requests to trigger launchd properly to get X going. That is a different issue, of which I am well aware. Essentially, launchd listens on a unix domain socket named something like /tmp/launch-.../:0 (where the ... is some random collection of alphanumerics), and DISPLAY is set to this value. When something connects, launchd fires up X11, which takes over the socket. Once X11 is up and running, though, the X server listens in addition to the unix domain socket at /tmp/.X11-unix/X0 (aka unix:0) and tcp port 6000 (aka localhost:0). I have made sure X11 is already running before I try opening an x display with clx, and I certainly don't even try to point it at the /tmp/launch-.../:0 socket (I am not sure it is even possible). To be absolutely sure, I even removed that value of DISPLAY from the environment. It did not help. - Harald |
From: Michael W. <mic...@fo...> - 2009-03-11 13:56:13
|
On Mar 11, 2009, at 08:21 , Harald Hanche-Olsen wrote: > (xlib:open-display "unix") results in Works for me with darcs CLX from <http://common-lisp.net/~crhodes/clx> (whatever clbuild pulls in). In particular, I believe the following patch is crucial: Sun Jun 22 19:53:27 CEST 2008 cs...@ca... * launchd-darwin-support From Rudi Schlatte -- Cheers, Michael |