From js at alien8.de Wed Mar 17 01:05:08 2010 From: js at alien8.de (Julian Stecklina) Date: Wed, 17 Mar 2010 02:05:08 +0100 Subject: [clx-devel] clx failure Message-ID: <87iq8v69mj.fsf@tabernacle.localhost> The following message is a courtesy copy of an article that has been posted to gmane.lisp.ecl.general as well. Hello, this is with a recent ECL from git: % echo $DISPLAY :0.0 % ecl ECL (Embeddable Common-Lisp) 10.3.1 [...] > (require :clx) ;;; Loading #P"/home/julian/local-install/lib/ecl-10.3.1/clx.fas" ;;; Loading #P"/home/julian/local-install/lib/ecl-10.3.1/sockets.fas" ("CLX" "SB-BSD-SOCKETS" "SOCKETS") > (xlib:open-default-display) X-Error: Connection failure to X11.0 server display 0: No protocol specified Available restarts: 1. (RESTART-TOPLEVEL) Go back to Top-Level REPL. Broken at XLIB::X-ERROR. File: "src:clx;dependent.lisp.NEWEST" (Position #76750) >> :backtrace Backtrace: > XLIB::X-ERROR > xlib::display-connect > xlib:open-display > xlib:open-default-display > si:bytecodes [Evaluation of: (xlib:open-default-display)] Staring at display-connect doesn't reveal what's the real cause. Any hints? Regards, -- Julian Stecklina The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners - Ernst Jan Plugge From eric.marsden at free.fr Wed Mar 17 08:12:33 2010 From: eric.marsden at free.fr (Eric Marsden) Date: Wed, 17 Mar 2010 09:12:33 +0100 Subject: [clx-devel] clx failure References: <87iq8v69mj.fsf@tabernacle.localhost> Message-ID: <87pr335pu6.fsf@free.fr> >>>>> "js" == Julian Stecklina writes: js> X-Error: Connection failure to X11.0 server display 0: No protocol specified Possibly CLX will work better on ECL with the following patch. diff -rN -u old-csr-clx/dependent.lisp new-csr-clx/dependent.lisp --- old-csr-clx/dependent.lisp 2010-03-17 09:10:36.000000000 +0100 +++ new-csr-clx/dependent.lisp 2010-03-17 09:10:36.000000000 +0100 @@ -2873,10 +2873,9 @@ "Return the same hostname as gethostname(3) would" ;; machine-instance probably works on a lot of lisps, but clisp is not ;; one of them - #+(or cmu sbcl) (machine-instance) + #+(or cmu sbcl ecl) (machine-instance) ;; resources-pathname was using short-site-name for this purpose #+excl (short-site-name) - #+ecl (si:getenv "HOST") #+clisp (let ((s (machine-instance))) (subseq s 0 (position #\Space s))) #-(or excl cmu sbcl ecl clisp) (error "get-host-name not implemented")) -- Eric Marsden