From lvalais at lrde.epita.fr Tue May 16 12:01:13 2017 From: lvalais at lrde.epita.fr (lvalais) Date: Tue, 16 May 2017 14:01:13 +0200 Subject: don't recognize component type REQUIRE-SYSTEM. Message-ID: <80886d4231f2b7c15acce40bd797f2e0@lrde.epita.fr> Hi, I'm trying to run slime for the first time with sbcl. Previously, I was using clisp. I'm using for now the pre-compiled version of sbcl. When I try to start slime, I get the errors shown below. Can someone help? Kind Regards Leo $ sbcl sbcl This is SBCL 1.1.6.0-3c5581a, an implementation of ANSI Common Lisp. More information about SBCL is available at . SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. * (load "~/.emacs.d/lisp/slime/swank-loader.lisp") (load "~/.emacs.d/lisp/slime/swank-loader.lisp") T * (swank-loader:init) (swank-loader:init) ASDF could not load sb-bsd-sockets because Error while trying to load definition for system sb-bsd-sockets from pathname /usr/local/lib/sbcl/contrib/sb-bsd-sockets.asd: don't recognize component type REQUIRE-SYSTEM. ;; ;; Error compiling ~/.emacs.d/lisp/slime/swank/sbcl.lisp: ;; Error while trying to load definition for system sb-bsd-sockets from ;; pathname /usr/local/lib/sbcl/contrib/sb-bsd-sockets.asd: ;; don't recognize component type REQUIRE-SYSTEM ;; debugger invoked on a LOAD-SYSTEM-DEFINITION-ERROR: Error while trying to load definition for system sb-bsd-sockets from pathname /usr/local/lib/sbcl/contrib/sb-bsd-sockets.asd: don't recognize component type REQUIRE-SYSTEM Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [RETRY ] Retry EVAL of current toplevel form. 1: [CONTINUE ] Ignore error and continue loading file "/usr/local/lib/sbcl/contrib/sb-bsd-sockets.asd". 2: [ABORT ] Abort loading file "/usr/local/lib/sbcl/contrib/sb-bsd-sockets.asd". 3: [REINITIALIZE-SOURCE-REGISTRY-AND-RETRY] Retry finding system sb-bsd-sockets after reinitializing the source-registry. 4: Exit debugger, returning to top level. ((FLET #:LAMBDA2229 :IN ASDF::LOAD-SYSDEF) #) 0] From luismbo at gmail.com Tue May 16 12:23:16 2017 From: luismbo at gmail.com (=?UTF-8?Q?Lu=C3=ADs_Oliveira?=) Date: Tue, 16 May 2017 12:23:16 +0000 Subject: don't recognize component type REQUIRE-SYSTEM. In-Reply-To: <80886d4231f2b7c15acce40bd797f2e0@lrde.epita.fr> References: <80886d4231f2b7c15acce40bd797f2e0@lrde.epita.fr> Message-ID: That SBCL version is 4 years old, isn't it? Can you try with a more recent one? Cheers, Lu?s On Tue, May 16, 2017, 21:02 lvalais wrote: > Hi, I'm trying to run slime for the first time with sbcl. Previously, > I was using clisp. I'm using for now the pre-compiled version of sbcl. > When I try to start slime, I get the errors shown below. > > Can someone help? > > Kind Regards > Leo > > $ sbcl > sbcl > This is SBCL 1.1.6.0-3c5581a, an implementation of ANSI Common Lisp. > More information about SBCL is available at . > > SBCL is free software, provided as is, with absolutely no warranty. > It is mostly in the public domain; some portions are provided under > BSD-style licenses. See the CREDITS and COPYING files in the > distribution for more information. > * (load "~/.emacs.d/lisp/slime/swank-loader.lisp") > (load "~/.emacs.d/lisp/slime/swank-loader.lisp") > > T > * (swank-loader:init) > (swank-loader:init) > ASDF could not load sb-bsd-sockets because > Error while trying to load definition for system sb-bsd-sockets from > pathname > /usr/local/lib/sbcl/contrib/sb-bsd-sockets.asd: > don't recognize component type REQUIRE-SYSTEM. > ;; > ;; Error compiling ~/.emacs.d/lisp/slime/swank/sbcl.lisp: > ;; Error while trying to load definition for system sb-bsd-sockets > from > ;; pathname /usr/local/lib/sbcl/contrib/sb-bsd-sockets.asd: > ;; don't recognize component type REQUIRE-SYSTEM > ;; > > debugger invoked on a LOAD-SYSTEM-DEFINITION-ERROR: > Error while trying to load definition for system sb-bsd-sockets from > pathname > /usr/local/lib/sbcl/contrib/sb-bsd-sockets.asd: > don't recognize component type REQUIRE-SYSTEM > > Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL. > > restarts (invokable by number or by possibly-abbreviated name): > 0: [RETRY ] Retry EVAL of current > toplevel form. > 1: [CONTINUE ] Ignore error and continue > loading file "/usr/local/lib/sbcl/contrib/sb-bsd-sockets.asd". > 2: [ABORT ] Abort loading file > "/usr/local/lib/sbcl/contrib/sb-bsd-sockets.asd". > 3: [REINITIALIZE-SOURCE-REGISTRY-AND-RETRY] Retry finding system > sb-bsd-sockets after > reinitializing the > source-registry. > 4: Exit debugger, returning > to top > level. > > ((FLET #:LAMBDA2229 :IN ASDF::LOAD-SYSDEF) > #) > 0] > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nlevine at ravenpack.com Thu May 25 09:49:42 2017 From: nlevine at ravenpack.com (Nick Levine) Date: Thu, 25 May 2017 11:49:42 +0200 Subject: 2nd repl for same inferior lisp In-Reply-To: References: Message-ID: Finally got around to trying your suggestion. It killed my original repl (along with the background task that this was performing) and so gained me nothing. - n On 27 March 2017 at 16:41, Mark Evenson wrote: > > > On 3/17/17 11:14, Jim Newton wrote: > > Hi, > > Can someone tell me how to (or if it is possible to) create a second repl > > buffer for the same inferior lisp process. Maybe this is not supported, > > because when I look in the slime manual, it seems to always refer to "THE > > REPL buffer for the current SLIME connection? > > If you want to start an additional inferior lisp process for the same > implementation (not strictly "the same inferior lisp process" but maybe > what you mean?): > > 1) visiting the REPL issue a M-x rename-uniquely > > 2) You may now start an additional REPL for the associated inferior lisp > via the usual M-x slime invocation. > > -- > "No, this is not a disentanglement, but a progressive /knotting-into/." > > -------------- next part -------------- An HTML attachment was scrubbed... URL: