You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(2) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(8) |
Jun
|
Jul
(2) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
2002 |
Jan
|
Feb
(2) |
Mar
(3) |
Apr
|
May
(5) |
Jun
|
Jul
|
Aug
(2) |
Sep
(3) |
Oct
|
Nov
|
Dec
(8) |
2003 |
Jan
(5) |
Feb
(4) |
Mar
(14) |
Apr
|
May
(27) |
Jun
(10) |
Jul
(3) |
Aug
(28) |
Sep
(27) |
Oct
(3) |
Nov
(14) |
Dec
(19) |
2004 |
Jan
(32) |
Feb
(15) |
Mar
(21) |
Apr
(69) |
May
(18) |
Jun
(15) |
Jul
(23) |
Aug
(14) |
Sep
(38) |
Oct
(20) |
Nov
(76) |
Dec
(27) |
2005 |
Jan
(24) |
Feb
(32) |
Mar
(39) |
Apr
(65) |
May
(69) |
Jun
(37) |
Jul
(32) |
Aug
(28) |
Sep
(28) |
Oct
(17) |
Nov
(30) |
Dec
(24) |
2006 |
Jan
(45) |
Feb
(38) |
Mar
(19) |
Apr
(26) |
May
(19) |
Jun
(29) |
Jul
(13) |
Aug
(26) |
Sep
(53) |
Oct
(46) |
Nov
(40) |
Dec
(85) |
2007 |
Jan
(45) |
Feb
(51) |
Mar
(69) |
Apr
(48) |
May
(75) |
Jun
(35) |
Jul
(35) |
Aug
(25) |
Sep
(11) |
Oct
(16) |
Nov
(9) |
Dec
(59) |
2008 |
Jan
(36) |
Feb
(17) |
Mar
(28) |
Apr
(13) |
May
(1) |
Jun
(25) |
Jul
(24) |
Aug
(52) |
Sep
(19) |
Oct
(52) |
Nov
(43) |
Dec
(80) |
2009 |
Jan
(33) |
Feb
(30) |
Mar
(18) |
Apr
(15) |
May
(29) |
Jun
(58) |
Jul
(48) |
Aug
(35) |
Sep
(52) |
Oct
(59) |
Nov
(46) |
Dec
(31) |
2010 |
Jan
(26) |
Feb
(45) |
Mar
(55) |
Apr
(59) |
May
(8) |
Jun
(24) |
Jul
(43) |
Aug
(31) |
Sep
(43) |
Oct
(33) |
Nov
(41) |
Dec
(19) |
2011 |
Jan
(17) |
Feb
(31) |
Mar
(5) |
Apr
(31) |
May
(17) |
Jun
(28) |
Jul
(15) |
Aug
(38) |
Sep
(21) |
Oct
(25) |
Nov
(21) |
Dec
(21) |
2012 |
Jan
(9) |
Feb
(22) |
Mar
(17) |
Apr
(16) |
May
(58) |
Jun
(13) |
Jul
(40) |
Aug
(12) |
Sep
(10) |
Oct
(10) |
Nov
(14) |
Dec
(4) |
2013 |
Jan
(9) |
Feb
(8) |
Mar
(17) |
Apr
(10) |
May
|
Jun
(9) |
Jul
(1) |
Aug
(7) |
Sep
(8) |
Oct
(22) |
Nov
(9) |
Dec
(6) |
2014 |
Jan
(30) |
Feb
(55) |
Mar
(38) |
Apr
(15) |
May
(7) |
Jun
(17) |
Jul
(15) |
Aug
(13) |
Sep
(21) |
Oct
(29) |
Nov
(7) |
Dec
(10) |
2015 |
Jan
(11) |
Feb
(19) |
Mar
(32) |
Apr
(17) |
May
(5) |
Jun
(3) |
Jul
(9) |
Aug
(7) |
Sep
(19) |
Oct
(3) |
Nov
(31) |
Dec
(23) |
2016 |
Jan
(11) |
Feb
(5) |
Mar
(8) |
Apr
(10) |
May
(15) |
Jun
(1) |
Jul
(11) |
Aug
(9) |
Sep
(11) |
Oct
(1) |
Nov
(26) |
Dec
(7) |
2017 |
Jan
(18) |
Feb
(19) |
Mar
(40) |
Apr
(6) |
May
(12) |
Jun
(1) |
Jul
(14) |
Aug
(21) |
Sep
(27) |
Oct
(22) |
Nov
(42) |
Dec
(3) |
2018 |
Jan
(9) |
Feb
(7) |
Mar
(31) |
Apr
(5) |
May
(7) |
Jun
|
Jul
(6) |
Aug
(34) |
Sep
(2) |
Oct
(8) |
Nov
(29) |
Dec
(7) |
2019 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(62) |
May
(18) |
Jun
(12) |
Jul
(30) |
Aug
(8) |
Sep
(4) |
Oct
(8) |
Nov
(6) |
Dec
(12) |
2020 |
Jan
(24) |
Feb
(4) |
Mar
(11) |
Apr
(16) |
May
(6) |
Jun
(59) |
Jul
(51) |
Aug
(18) |
Sep
(32) |
Oct
(19) |
Nov
(12) |
Dec
(29) |
2021 |
Jan
(11) |
Feb
(27) |
Mar
(30) |
Apr
(10) |
May
(29) |
Jun
(14) |
Jul
(10) |
Aug
(3) |
Sep
(12) |
Oct
(10) |
Nov
(18) |
Dec
(19) |
2022 |
Jan
(11) |
Feb
(8) |
Mar
(21) |
Apr
(30) |
May
(3) |
Jun
(2) |
Jul
(16) |
Aug
(9) |
Sep
(4) |
Oct
(2) |
Nov
(17) |
Dec
(10) |
2023 |
Jan
(16) |
Feb
(21) |
Mar
(42) |
Apr
(8) |
May
(7) |
Jun
(32) |
Jul
(3) |
Aug
(22) |
Sep
(11) |
Oct
(3) |
Nov
(16) |
Dec
(12) |
2024 |
Jan
(8) |
Feb
(15) |
Mar
(32) |
Apr
(31) |
May
(23) |
Jun
(51) |
Jul
(13) |
Aug
(19) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
From: Richard M K. <kr...@pr...> - 2008-04-03 23:49:31
|
"Evan Monroig" writes: > I would like to use posix file locks and have searched around to use > sb-posix:fcntl with the commands sb-posix:f-setlk and > sb-posix:f-getlk, but I cannot get it to work. > > According to the sbcl manual [1] there should be a class > sb-posix:flock to use with the above command, but it seems not to be > available in my sbcl installation. > > Is it that it is available only with the most recent sbcl? Yes, support for struct flock was added just in the last several weeks, I think. (The online manual documents the latest version in CVS.) So you could upgrade now, or else perhaps try lockf(3), if that suits your needs. -- Richard |
From: Evan M. <eva...@gm...> - 2008-04-03 23:36:07
|
Hi, I would like to use posix file locks and have searched around to use sb-posix:fcntl with the commands sb-posix:f-setlk and sb-posix:f-getlk, but I cannot get it to work. According to the sbcl manual [1] there should be a class sb-posix:flock to use with the above command, but it seems not to be available in my sbcl installation. Is it that it is available only with the most recent sbcl? I run sbcl 1.0.6 on ubuntu gutsy on a 32bit intel platform. Thanks in advance, Evan [1] http://www.sbcl.org/manual/Lisp-objects-and-C-structures.html#Lisp-objects-and-C-structures |
From: Juho S. <js...@ik...> - 2008-04-03 09:23:24
|
Roman Budzianowski <ro...@bu...> writes: > Here is another example. The file being compiled has this code at the > top: > > (unless (find-package :gbbopen-tools) > (defpackage :gbbopen-tools > (:use :common-lisp))) > > (in-package :gbbopen-tools) > > Is this supposed to work? No. Since you've wrapped the DEFPACKAGE in an UNLESS, it does not have a compile-time effect. Either use a reader conditional instead of UNLESS, or wrap the whole form in an EVAL-WHEN. -- Juho Snellman |
From: Roman B. <ro...@bu...> - 2008-04-03 06:11:24
|
Here is another example. The file being compiled has this code at the top: (unless (find-package :gbbopen-tools) (defpackage :gbbopen-tools (:use :common-lisp))) (in-package :gbbopen-tools) Is this supposed to work? The name "GBBOPEN-TOOLS" does not designate any package. [Condition of type SB-KERNEL:SIMPLE-PACKAGE-ERROR] Restarts: 0: [ABORT] Return to SLIME's top level. 1: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl- thread" {100260C1F1}>) Backtrace: 0: (SB-INT:%FIND-PACKAGE-OR-LOSE "GBBOPEN-TOOLS") 1: (SB-INT:FIND-UNDELETED-PACKAGE-OR-LOSE "GBBOPEN-TOOLS") 2: (NIL) 3: (SB-INT:SIMPLE-EVAL-IN-LEXENV (SETQ *PACKAGE* (SB-INT:FIND- UNDELETED-PACKAGE-OR-LOSE "GBBOPEN-TOOLS")) #<NULL-LEXENV>) 4: ((FLET SB-C::DEFAULT-PROCESSOR) (SETQ *PACKAGE* (SB-INT:FIND- UNDELETED-PACKAGE-OR-LOSE "GBBOPEN-TOOLS"))) 5: (SB-C::PROCESS-TOPLEVEL-FORM (SETQ *PACKAGE* (SB-INT:FIND- UNDELETED-PACKAGE-OR-LOSE "GBBOPEN-TOOLS")) ((EVAL-WHEN (:COMPILE- TOPLEVEL :LOAD-TOPLEVEL :EXECUTE) (SETQ *PACKAGE* #)) SB-C::ORIGINAL- SOURCE-START 0 1) (:COMPILE-TOPLEVEL)) 6: (SB-C::PROCESS-TOPLEVEL-PROGN ((SETQ *PACKAGE* (SB-INT:FIND- UNDELETED-PACKAGE-OR-LOSE "GBBOPEN-TOOLS"))) ((EVAL-WHEN (:COMPILE- TOPLEVEL :LOAD-TOPLEVEL :EXECUTE) (SETQ *PACKAGE* #)) SB-C::ORIGINAL- SOURCE-START 0 1) (:COMPILE-TOPLEVEL)) 7: (SB-C::PROCESS-TOPLEVEL-FORM (EVAL-WHEN (:COMPILE-TOPLEVEL :LOAD- TOPLEVEL :EXECUTE) (SETQ *PACKAGE* (SB-INT:FIND-UNDELETED-PACKAGE-OR- LOSE "GBBOPEN-TOOLS"))) (SB-C::ORIGINAL-SOURCE-START 0 1) NIL) 8: ((FLET SB-C::DEFAULT-PROCESSOR) (IN-PACKAGE :GBBOPEN-TOOLS)) 9: (SB-C::PROCESS-TOPLEVEL-FORM (IN-PACKAGE :GBBOPEN-TOOLS) (SB- C::ORIGINAL-SOURCE-START 0 1) NIL) 10: (SB-C::SUB-SUB-COMPILE-FILE #<SB-C::SOURCE-INFO >) 11: ((LAMBDA NIL)) 12: (SB-C::%WITH-COMPILATION-UNIT #<CLOSURE (LAMBDA NIL) {10039DE259}>) 13: (SB-C::SUB-COMPILE-FILE #<SB-C::SOURCE-INFO >) 14: (COMPILE-FILE #P"/home/.../Third-Party/GBBOpen/Source/tools/ preamble.lisp") On Apr 2, 2008, at 9:07 PM, Roman Budzianowski wrote: > Hi, > > I am having some problems when loading multiple packages in sbcl. > This is the smallest example with public software. > It seems strange that loading gbbopen causes warnings about swank. > In any case I have no idea what the message (WARNING: SWANK used to > use the following packages:) means and why it's there. > I'd appreciate an explanation. > > Thanks, > > Roman > > > [roman@superdog PQ-sbcl$ sbcl -server 4005 > This is SBCL 1.0.12, an implementation of ANSI Common Lisp. > More information about SBCL is available at <http://www.sbcl.org/>. > > 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. > ; loading system definition from /home/slime/swank.asd into > #<PACKAGE "ASDF0"> > ; registering #<SYSTEM :SWANK {1002720D91}> as SWANK > ; loading #P"/home/roman/.slime/fasl/2008-03-18/sbcl-1.0.12-linux- > x86-64/swank-backend.fasl" > ; loading #P"/home/roman/.slime/fasl/2008-03-18/sbcl-1.0.12-linux- > x86-64/swank-source-path-parser.fasl" > ; loading #P"/home/roman/.slime/fasl/2008-03-18/sbcl-1.0.12-linux- > x86-64/swank-source-file-cache.fasl" > ; loading #P"/home/roman/.slime/fasl/2008-03-18/sbcl-1.0.12-linux- > x86-64/swank-sbcl.fasl" > STYLE-WARNING: redefining EMACS-INSPECT (#<BUILT-IN-CLASS T>) in > DEFMETHOD > ; loading #P"/home/roman/.slime/fasl/2008-03-18/sbcl-1.0.12-linux- > x86-64/swank-gray.fasl" > STYLE-WARNING: > implicitly creating new generic function STREAM-READ-CHAR-WILL- > HANG-P > ; loading #P"/home/roman/.slime/fasl/2008-03-18/sbcl-1.0.12-linux- > x86-64/swank.fasl" > server: (-server 4005) port: 4005 > WARNING: These Swank interfaces are unimplemented: > (CALLS-WHO DISASSEMBLE-FRAME SLDB-BREAK-AT-START SLDB-BREAK-ON-RETURN > WHO-SPECIALIZES) > ;; Swank started at port: 4005. > * (load "Third-Party/GBBOpen/startup.lisp") > > ;;; > ------------------------------------------------------------------------ > ;;; Mini-Module System 1.2 > ;;; > ;;; Developed and supported by the GBBopen Project (http:/ > GBBopen.org/) > ;;; (See http://GBBopen.org/downloads/LICENSE for license details.) > ;;; > ------------------------------------------------------------------------ > > STYLE-WARNING: redefining SB-IMPL::UNPARSE-UNIX-PIECE in DEFUN > WARNING: SWANK used to use the following packages: > (#<PACKAGE "SWANK-BACKEND">) > See also: > The ANSI Standard, Macro DEFPACKAGE > WARNING: SWANK also exports the following symbols: > (SWANK:*USE-DEDICATED-OUTPUT-STREAM* SWANK-BACKEND:EMACS-INSPECT > SWANK:QUIT-INSPECTOR SWANK:*LOG-EVENTS* SWANK:XREF > SWANK:INTERACTIVE-EVAL-REGION SWANK:STARTUP-MULTIPROCESSING > SWANK:INSPECTOR-NEXT SWANK:THROW-TO-TOPLEVEL SWANK:*GLOBAL-DEBUGGER* > SWANK:SWANK-COMPILER-MACROEXPAND SWANK:SLDB-NEXT SWANK:INVOKE-NTH- > RESTART > SWANK:OPERATOR-ARGLIST SWANK:FIND-DEFINITIONS-FOR-EMACS > SWANK:DESCRIBE-INSPECTEE SWANK:SLDB-RETURN-FROM-FRAME > SWANK:EVAL-AND-GRAB-OUTPUT SWANK:LIST-THREADS > SWANK:FIND-DEFINITION-FOR-THING SWANK-BACKEND:PROFILE-RESET > SWANK:INSPECTOR-POP SWANK:INSPECT-FRAME-VAR SWANK:CREATE-SERVER > SWANK:QUIT-THREAD-BROWSER SWANK:COMMIT-EDITED-VALUE SWANK:KILL-NTH- > THREAD > SWANK:SWANK-MACROEXPAND SWANK:COMPILE-FILE-FOR-EMACS > SWANK-BACKEND:UNPROFILE-ALL SWANK:LIST-ALL-PACKAGE-NAMES > SWANK:SLDB-CONTINUE > SWANK:SET-PACKAGE SWANK:START-SERVER SWANK:SLDB-BREAK SWANK:SWANK- > REQUIRE > SWANK:INSPECTOR-RANGE SWANK:DEBUG-NTH-THREAD SWANK:LISTENER-EVAL > SWANK:COMPILE-STRING-FOR-EMACS SWANK:*COMMUNICATION-STYLE* > SWANK-BACKEND:SET-DEFAULT-DIRECTORY SWANK:INSPECT-NTH-PART > SWANK-BACKEND:FRAME-SOURCE-LOCATION-FOR-EMACS SWANK:VALUE-FOR- > EDITING > SWANK:INSPECTOR-NTH-PART SWANK:DEBUGGER-INFO-FOR-EMACS > SWANK:SWANK-COMPILER-MACROEXPAND-1 SWANK:SLDB-BREAK-WITH-DEFAULT- > DEBUGGER > SWANK:DESCRIBE-SYMBOL SWANK:SLDB-OUT SWANK:START-SWANK-SERVER-IN- > THREAD > SWANK:*DEFAULT-WORKER-THREAD-BINDINGS* SWANK:TOGGLE-PROFILE- > FDEFINITION > SWANK:*SWANK-PPRINT-BINDINGS* SWANK:EVAL-STRING-IN-FRAME > SWANK:TAKE-INPUT > SWANK:SWANK-MACROEXPAND-1 SWANK:RE-EVALUATE-DEFVAR > SWANK:REDIRECT-TRACE-OUTPUT SWANK:FRAME-CATCH-TAGS-FOR-EMACS > SWANK:DOCUMENTATION-SYMBOL SWANK:DISASSEMBLE-SYMBOL SWANK:UNTRACE- > ALL > SWANK:LOAD-FILE SWANK:SWANK-DEBUGGER-HOOK SWANK:PRINT-INDENTATION- > LOSSAGE > SWANK:SWANK-TOGGLE-TRACE SWANK:INSPECT-IN-FRAME SWANK:SWANK- > MACROEXPAND-ALL > SWANK:STATE-STACK SWANK:DESCRIBE-DEFINITION-FOR-EMACS > SWANK:*GLOBALLY-REDIRECT-IO* SWANK-BACKEND:SLDB-BREAK-ON-RETURN > SWANK-BACKEND:RESTART-FRAME SWANK:*DEDICATED-OUTPUT-STREAM-PORT* > SWANK:SIMPLE-BREAK SWANK:PPRINT-EVAL-STRING-IN-FRAME > SWANK:*MACROEXPAND-PRINTER-BINDINGS* SWANK-BACKEND:DEFAULT-DIRECTORY > SWANK:ED-IN-EMACS SWANK:DESCRIBE-FUNCTION SWANK:INTERACTIVE-EVAL > SWANK:INIT-INSPECTOR SWANK:CONNECTION-INFO SWANK:SLDB-DISASSEMBLE > SWANK:PPRINT-EVAL SWANK:INVOKE-NTH-RESTART-FOR-EMACS > SWANK:*CONFIGURE-EMACS-INDENTATION* SWANK:INSPECT-CURRENT-CONDITION > SWANK:*LOG-OUTPUT* SWANK:UNDEFINE-FUNCTION SWANK:SLDB-STEP > SWANK-BACKEND:PROFILE-PACKAGE SWANK:*RECORD-REPL-RESULTS* > SWANK:COMPILER-NOTES-FOR-EMACS SWANK:MOP SWANK:INSPECTOR-REINSPECT > SWANK-BACKEND:BUFFER-FIRST-CHANGE SWANK:SLDB-ABORT > SWANK:FRAME-LOCALS-FOR-EMACS SWANK:IO-SPEED-TEST > SWANK:INSPECTOR-CALL-NTH-ACTION SWANK:INSPECT-IN-EMACS > SWANK:UPDATE-INDENTATION-INFORMATION SWANK:*READTABLE-ALIST* > SWANK-BACKEND:PROFILE-REPORT SWANK:*SLDB-PRINTER-BINDINGS* > SWANK:RESTART-SERVER SWANK-BACKEND:QUIT-LISP > SWANK-BACKEND:PROFILED-FUNCTIONS SWANK:PPRINT-INSPECTOR-PART > SWANK:APROPOS-LIST-FOR-EMACS SWANK:BACKTRACE SWANK:SIMPLE- > COMPLETIONS > SWANK:STOP-SERVER SWANK:*DONT-CLOSE* SWANK:*DEBUG-ON-SWANK-ERROR* > SWANK:COMPILE-FILE-IF-NEEDED) > See also: > The ANSI Standard, Macro DEFPACKAGE > T > * > |
From: Roman B. <ro...@bu...> - 2008-04-03 04:07:41
|
Hi, I am having some problems when loading multiple packages in sbcl. This is the smallest example with public software. It seems strange that loading gbbopen causes warnings about swank. In any case I have no idea what the message (WARNING: SWANK used to use the following packages:) means and why it's there. I'd appreciate an explanation. Thanks, Roman [roman@superdog PQ-sbcl$ sbcl -server 4005 This is SBCL 1.0.12, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>. 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. ; loading system definition from /home/slime/swank.asd into #<PACKAGE "ASDF0"> ; registering #<SYSTEM :SWANK {1002720D91}> as SWANK ; loading #P"/home/roman/.slime/fasl/2008-03-18/sbcl-1.0.12-linux- x86-64/swank-backend.fasl" ; loading #P"/home/roman/.slime/fasl/2008-03-18/sbcl-1.0.12-linux- x86-64/swank-source-path-parser.fasl" ; loading #P"/home/roman/.slime/fasl/2008-03-18/sbcl-1.0.12-linux- x86-64/swank-source-file-cache.fasl" ; loading #P"/home/roman/.slime/fasl/2008-03-18/sbcl-1.0.12-linux- x86-64/swank-sbcl.fasl" STYLE-WARNING: redefining EMACS-INSPECT (#<BUILT-IN-CLASS T>) in DEFMETHOD ; loading #P"/home/roman/.slime/fasl/2008-03-18/sbcl-1.0.12-linux- x86-64/swank-gray.fasl" STYLE-WARNING: implicitly creating new generic function STREAM-READ-CHAR-WILL- HANG-P ; loading #P"/home/roman/.slime/fasl/2008-03-18/sbcl-1.0.12-linux- x86-64/swank.fasl" server: (-server 4005) port: 4005 WARNING: These Swank interfaces are unimplemented: (CALLS-WHO DISASSEMBLE-FRAME SLDB-BREAK-AT-START SLDB-BREAK-ON-RETURN WHO-SPECIALIZES) ;; Swank started at port: 4005. * (load "Third-Party/GBBOpen/startup.lisp") ;;; ------------------------------------------------------------------------ ;;; Mini-Module System 1.2 ;;; ;;; Developed and supported by the GBBopen Project (http:/ GBBopen.org/) ;;; (See http://GBBopen.org/downloads/LICENSE for license details.) ;;; ------------------------------------------------------------------------ STYLE-WARNING: redefining SB-IMPL::UNPARSE-UNIX-PIECE in DEFUN WARNING: SWANK used to use the following packages: (#<PACKAGE "SWANK-BACKEND">) See also: The ANSI Standard, Macro DEFPACKAGE WARNING: SWANK also exports the following symbols: (SWANK:*USE-DEDICATED-OUTPUT-STREAM* SWANK-BACKEND:EMACS-INSPECT SWANK:QUIT-INSPECTOR SWANK:*LOG-EVENTS* SWANK:XREF SWANK:INTERACTIVE-EVAL-REGION SWANK:STARTUP-MULTIPROCESSING SWANK:INSPECTOR-NEXT SWANK:THROW-TO-TOPLEVEL SWANK:*GLOBAL-DEBUGGER* SWANK:SWANK-COMPILER-MACROEXPAND SWANK:SLDB-NEXT SWANK:INVOKE-NTH- RESTART SWANK:OPERATOR-ARGLIST SWANK:FIND-DEFINITIONS-FOR-EMACS SWANK:DESCRIBE-INSPECTEE SWANK:SLDB-RETURN-FROM-FRAME SWANK:EVAL-AND-GRAB-OUTPUT SWANK:LIST-THREADS SWANK:FIND-DEFINITION-FOR-THING SWANK-BACKEND:PROFILE-RESET SWANK:INSPECTOR-POP SWANK:INSPECT-FRAME-VAR SWANK:CREATE-SERVER SWANK:QUIT-THREAD-BROWSER SWANK:COMMIT-EDITED-VALUE SWANK:KILL-NTH- THREAD SWANK:SWANK-MACROEXPAND SWANK:COMPILE-FILE-FOR-EMACS SWANK-BACKEND:UNPROFILE-ALL SWANK:LIST-ALL-PACKAGE-NAMES SWANK:SLDB-CONTINUE SWANK:SET-PACKAGE SWANK:START-SERVER SWANK:SLDB-BREAK SWANK:SWANK- REQUIRE SWANK:INSPECTOR-RANGE SWANK:DEBUG-NTH-THREAD SWANK:LISTENER-EVAL SWANK:COMPILE-STRING-FOR-EMACS SWANK:*COMMUNICATION-STYLE* SWANK-BACKEND:SET-DEFAULT-DIRECTORY SWANK:INSPECT-NTH-PART SWANK-BACKEND:FRAME-SOURCE-LOCATION-FOR-EMACS SWANK:VALUE-FOR- EDITING SWANK:INSPECTOR-NTH-PART SWANK:DEBUGGER-INFO-FOR-EMACS SWANK:SWANK-COMPILER-MACROEXPAND-1 SWANK:SLDB-BREAK-WITH-DEFAULT- DEBUGGER SWANK:DESCRIBE-SYMBOL SWANK:SLDB-OUT SWANK:START-SWANK-SERVER-IN- THREAD SWANK:*DEFAULT-WORKER-THREAD-BINDINGS* SWANK:TOGGLE-PROFILE- FDEFINITION SWANK:*SWANK-PPRINT-BINDINGS* SWANK:EVAL-STRING-IN-FRAME SWANK:TAKE-INPUT SWANK:SWANK-MACROEXPAND-1 SWANK:RE-EVALUATE-DEFVAR SWANK:REDIRECT-TRACE-OUTPUT SWANK:FRAME-CATCH-TAGS-FOR-EMACS SWANK:DOCUMENTATION-SYMBOL SWANK:DISASSEMBLE-SYMBOL SWANK:UNTRACE- ALL SWANK:LOAD-FILE SWANK:SWANK-DEBUGGER-HOOK SWANK:PRINT-INDENTATION- LOSSAGE SWANK:SWANK-TOGGLE-TRACE SWANK:INSPECT-IN-FRAME SWANK:SWANK- MACROEXPAND-ALL SWANK:STATE-STACK SWANK:DESCRIBE-DEFINITION-FOR-EMACS SWANK:*GLOBALLY-REDIRECT-IO* SWANK-BACKEND:SLDB-BREAK-ON-RETURN SWANK-BACKEND:RESTART-FRAME SWANK:*DEDICATED-OUTPUT-STREAM-PORT* SWANK:SIMPLE-BREAK SWANK:PPRINT-EVAL-STRING-IN-FRAME SWANK:*MACROEXPAND-PRINTER-BINDINGS* SWANK-BACKEND:DEFAULT-DIRECTORY SWANK:ED-IN-EMACS SWANK:DESCRIBE-FUNCTION SWANK:INTERACTIVE-EVAL SWANK:INIT-INSPECTOR SWANK:CONNECTION-INFO SWANK:SLDB-DISASSEMBLE SWANK:PPRINT-EVAL SWANK:INVOKE-NTH-RESTART-FOR-EMACS SWANK:*CONFIGURE-EMACS-INDENTATION* SWANK:INSPECT-CURRENT-CONDITION SWANK:*LOG-OUTPUT* SWANK:UNDEFINE-FUNCTION SWANK:SLDB-STEP SWANK-BACKEND:PROFILE-PACKAGE SWANK:*RECORD-REPL-RESULTS* SWANK:COMPILER-NOTES-FOR-EMACS SWANK:MOP SWANK:INSPECTOR-REINSPECT SWANK-BACKEND:BUFFER-FIRST-CHANGE SWANK:SLDB-ABORT SWANK:FRAME-LOCALS-FOR-EMACS SWANK:IO-SPEED-TEST SWANK:INSPECTOR-CALL-NTH-ACTION SWANK:INSPECT-IN-EMACS SWANK:UPDATE-INDENTATION-INFORMATION SWANK:*READTABLE-ALIST* SWANK-BACKEND:PROFILE-REPORT SWANK:*SLDB-PRINTER-BINDINGS* SWANK:RESTART-SERVER SWANK-BACKEND:QUIT-LISP SWANK-BACKEND:PROFILED-FUNCTIONS SWANK:PPRINT-INSPECTOR-PART SWANK:APROPOS-LIST-FOR-EMACS SWANK:BACKTRACE SWANK:SIMPLE- COMPLETIONS SWANK:STOP-SERVER SWANK:*DONT-CLOSE* SWANK:*DEBUG-ON-SWANK-ERROR* SWANK:COMPILE-FILE-IF-NEEDED) See also: The ANSI Standard, Macro DEFPACKAGE T * |
From: Jonathan G. <jga...@jo...> - 2008-04-02 03:50:49
|
Has anyone attempted a binding with KDE Smoke to allow SBCL to use Qt and KDE? Currently, Smoke supports Ruby, Perl, and even Java, apparently. I'm new to lisp but what I see I like a lot already. I'm interested in doing some heavy lifting if people are willing to help with the hard parts. References: http://techbase.kde.org/index.php?title=Development/Languages |
From: Dr. H. G. E. <he...@cy...> - 2008-03-29 09:33:38
|
Jeffrey Straszheim wrote: > Hello, > ..... > > P.S. What is quickest way to get an HTTP application server up and running on > SBCL? As so far no one mentioned Debian :-), I'm using Debian, (the nice thing is installing for 64 bit or 32 bit is all the same proceedure.) apt-get install sbcl ... ready to run. apt-get install hunchentool ... ready to run with all the other cl-libs needed. I add apt-get install cl-who ,.. nice thing for writing html. apt-get install slime. With these 4 lines you have all you need. I'm using hunchentoot alot with no problems. I have pages with some megabytes and the bottleneck is always the browser. From my point of view you do not need apache in front of it. It is stable and if you have a problem it is easyly solved, as slime puts you to the point of the error in the source code, down to http problems. I have used apache as a frontend before, and most of the problems came from that constellation. (but be careful, it is just my point of view :-) I'm running hunchentoot as a standalone on a server (32 bit and 64 bit) without a gui. To work on the server(s) I use ssh and screen (very nice, you are working on the server, dettach, go home reattach and continue working) If you want port 80 and not sbcl running as root, you need privbind. Here are my start file. I chmod u+s /usr/bin/privbind and add (setq inferior-lisp-program "/usr/bin/privbind -u helmut -g helmut /usr/bin/sbcl") to my .emacs and add screen -t Hunchentoot emacs -f slime to my .screenrc and add (require 'hunchentoot) (hunchentoot:start-server :port 80 :address <ip of eth0:1>) to my .sbclrc :-) and add sudo -H -u helmut screen -d -m to my /etc/init.d/screens .... even after an reboot I login (or ssh to the server), do a screen -R .... and be happy. Emacs-slime-sbcl running in a screen is one unit for me, and I use for each project always a new 'unit'. I have a simple script to create a new user with the files above to start an new project. <off topic> I'm also using git.</off topic> Now my server has many eth0:x's with many hunchentoolies, listening all on port 80 :-) Helmut |
From: Jeffrey S. <jst...@co...> - 2008-03-29 02:59:51
|
Thanks for the help. Compiling it myself worked, except people should be warned that Ubuntu does not provide the C header files by default -- that took a little bit to figure out. Brian Mastenbrook wrote: > > I would recommend staying away from distribution packages for SBCL. > Just download the latest binary from the web site, install it, and use > it to compile the latest sources. It's relatively straightforward; the > only thing that's even moderately tricky is building with threads. To > do that, create a file named "customize-target-features.lisp" in the > root of the SBCL sources containing something like: > > (lambda (list) (cons :sb-thread list)) > > Then just build SBCL as usual ("sh make.sh"). > > I'll let others answer the HTTP question as my views seem to be out of > the mainstream these days... > -- Jeffrey Straszheim jst...@co... |
From: Roman B. <ro...@bu...> - 2008-03-27 14:35:48
|
Thanks. This works. It seems that the dumped image doesn't behave in standard way in more ways. Here's an error I get on the top level when I type an extra paren - sbcl exists. No handler installed? How to save an image and preserve the top level loop? Roman [roman@usnam PQ-sbcl]$ sbcl --core concepts.core --no-userinit This is SBCL 1.0.12, an implementation of ANSI Common Lisp.More information about SBCL is available at <http://www.sbcl.org/>. SBCL is free software, provided as is, with absolutely no warranty.It is mostly in the public domain; some portions are provided underBSD- style licenses. See the CREDITS and COPYING files in thedistribution for more information. * (+ 1 2)) 3* 0: (BACKTRACE 20 #<SYNONYM-STREAM :SYMBOL *TERMINAL-IO* {10001EF5E1}>)1: ((LAMBDA (CONDITION HOOK)) #<SB-INT:SIMPLE-READER- ERROR {100CB9FB61}> #<unavailable argument>)2: (INVOKE-DEBUGGER #<SB-INT:SIMPLE-READER-ERROR {100CB9FB61}>)3: (INVOKE-DEBUGGER #<SB- INT:SIMPLE-READER-ERROR {100CB9FB61}>)4: (ERROR SB-INT:SIMPLE-READER- ERROR)5: (SB-INT:SIMPLE-READER-ERROR #<SYNONYM-STREAM :SYMBOL SB- SYS:*STDIN* {10001EF551}> "unmatched close parenthesis")6: (READ- PRESERVING-WHITESPACE #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDIN* {10001EF551}> NIL (NIL) T)7: (READ-PRESERVING-WHITESPACE #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDIN* {10001EF551}> NIL (NIL) NIL)8: (READ #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDIN* {10001EF551}> NIL (NIL) NIL)9: (EXTENDED-REPL-READ-FORM-FUN #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDIN* {10001EF551}> #<unavailable argument>)10: (SB-IMPL::REPL-FUN NIL)11: (SB-IMPL::REPL- FUN NIL)12: ((LAMBDA ()))13: ((LAMBDA ()))14: (SB-IMPL::%WITH-REBOUND- IO-SYNTAX #<CLOSURE (LAMBDA #) {100CB9E889}>)15: (SB-IMPL::TOPLEVEL- REPL NIL)16: (SB-IMPL::TOPLEVEL-INIT)17: ((LABELS SB-IMPL::RESTART- LISP)) Error: SB-INT:SIMPLE-READER-ERROR on #<SYNONYM-STREAM :SYMBOL SB- SYS:*STDIN* {10001EF551} >: unmatched close parenthesis [roman@usnam PQ-sbcl]$ On Mar 27, 2008, at 4:12 AM, Nikodemus Siivola wrote: > On Sun, Mar 23, 2008 at 1:13 AM, Roman Budzianowski > <ro...@bu...> wrote: > >> I am trying to figure out the magic that happens when I call sb- >> ext:save-lisp-and-die. >> >> I just started using sbcl. In a virgin image call to: >> (require :asdf) >> succeeds. >> >> In a saved image, run through --core argument, it fails. > > You need to set SBCL_HOME in the environment, or put the new core in > the same place as the old one. (SBCL_HOME defaults to the location of > the core: since your new core is not in the same place as the contrib > modules, SBCL doesn't find them.) > > Cheers, > > -- Nikodemus |
From: Nikodemus S. <nik...@ra...> - 2008-03-27 11:12:22
|
On Sun, Mar 23, 2008 at 1:13 AM, Roman Budzianowski <ro...@bu...> wrote: > I am trying to figure out the magic that happens when I call sb- > ext:save-lisp-and-die. > > I just started using sbcl. In a virgin image call to: (require :asdf) > succeeds. > > In a saved image, run through --core argument, it fails. You need to set SBCL_HOME in the environment, or put the new core in the same place as the old one. (SBCL_HOME defaults to the location of the core: since your new core is not in the same place as the contrib modules, SBCL doesn't find them.) Cheers, -- Nikodemus |
From: Martin R. <mar...@un...> - 2008-03-26 18:05:19
|
"Nikodemus Siivola" <nik...@ra...> writes: > To find contrib modules, SBCL_HOME needs to be set to /usr/local/lib/sbcl > (or where ever SBCL was installed.) If it is not set, SBCL uses the location > of the core file as the default. If Axiom uses a custom core, the default > will be wrong. Many thanks, that was indeed the reason! Martin |
From: Nikodemus S. <nik...@ra...> - 2008-03-26 16:59:32
|
On 26 Mar 2008 14:32:04 +0100, Martin Rubey <mar...@un...> wrote: > Dear all, > > I wanted to try the statistical profiler within axiom/fricas (compiled with > sbcl, of course), but failed. My sbcl is 1.0.6 on kubuntu gutsy. > > The strange thing is, it works if I just start sbcl, but does not from within > axiom/fricas, I get: > > (1) -> )lisp (require :sb-sprof) > > >> System error: > Don't know how to REQUIRE SB-SPROF. > See also: > The SBCL Manual, Variable SB-EXT:*MODULE-PROVIDER-FUNCTIONS* > The SBCL Manual, Function REQUIRE > > Any ideas? To find contrib modules, SBCL_HOME needs to be set to /usr/local/lib/sbcl (or where ever SBCL was installed.) If it is not set, SBCL uses the location of the core file as the default. If Axiom uses a custom core, the default will be wrong. Cheers, -- Nikodemus |
From: Martin R. <mar...@un...> - 2008-03-26 13:32:17
|
Dear all, I wanted to try the statistical profiler within axiom/fricas (compiled with sbcl, of course), but failed. My sbcl is 1.0.6 on kubuntu gutsy. The strange thing is, it works if I just start sbcl, but does not from within axiom/fricas, I get: (1) -> )lisp (require :sb-sprof) >> System error: Don't know how to REQUIRE SB-SPROF. See also: The SBCL Manual, Variable SB-EXT:*MODULE-PROVIDER-FUNCTIONS* The SBCL Manual, Function REQUIRE Any ideas? Martin |
From: Pascal B. <pj...@in...> - 2008-03-24 23:50:52
|
勇勇 writes: > hi,everyone: > > i am new to sbcl and lisp! when i use "setq" to define something in emacs(slime+sbcl) > SLIME 2006-04-20 > CL-USER> (setq a "dave") > > ; in: LAMBDA NIL > ; (SETQ A "dave") > ; > ; caught WARNING: > ; undefined variable: A > > ; > ; caught WARNING: > ; This variable is undefined: > ; A > ; > ; compilation unit finished > ; caught 2 WARNING conditions > "dave" > CL-USER> > > it sucess to define a ,but why it displays "caught WARNING" ? do i do something wrong? Yes, you did something wrong: you tried to assign an undefined variable. The CL standard doesn't define what should happen when you assign a variable that has not be defined. It leaves it up to the implementation, and each implementation may do something different. You can define a lexical variable with LET: (let (a) (setq a "dave") (print a) (values)) but of course, the variable A won't be defined outside of it's lexical scope. Or you can define a global dynamic variable with DEFVAR or DEFPARAMETER: (defvar *a*) (setq *a* "dave") (print *a*) But there is no way provided by CL to define a global lexical variable. (It's possible to get something having the same effects than a global lexical variable with symbol macros). Note that since dynamic varibles are special, there is this convention to name them surrounded by stars. The problem is that once you've declared a variable special (dynamic), any use of that variable will be special: (defvar s 0) (defun f () (print (list 'f '--> 's '= s)) (values)) (defun g () (let ((s 1)) (f) (values))) (g) prints: (F --> S = 1) -- __Pascal Bourguignon__ http://www.informatimago.com/ "Debugging? Klingons do not debug! Our software does not coddle the weak." |
From: 勇勇 <zho...@ya...> - 2008-03-24 13:52:15
|
hi,everyone: thanks for the answer of Lars, Matt, Nicolas, ChunTian ! I think i know how to fix the problem! for me it is the first time to use mail list!( i know it is weird:) ) i do not know whether reply the mail to someone who give me a answer or reply the mail to the sbcl-help! whatever, i just try to thank everyone! if i did something wrong, just tell me, so i can do it correctly! ps: to ChunTian ,yes i am a chinese! thanks for the help! --------------------------------- 雅虎邮箱,您的终生邮箱! |
From: Lars R. N. <lar...@gm...> - 2008-03-24 11:21:31
|
On Sun, 23 Mar 2008 08:40:39 +0800, 勇勇 wrote: > hi,everyone: > > i am new to sbcl and lisp! when i use "setq" to define something in > emacs(slime+sbcl) > SLIME 2006-04-20 > CL-USER> (setq a "dave") > > ; in: LAMBDA NIL > ; (SETQ A "dave") > ; > ; caught WARNING: > ; undefined variable: A > > ; > ; caught WARNING: > ; This variable is undefined: > ; A > ; > ; compilation unit finished > ; caught 2 WARNING conditions > "dave" > CL-USER> > > it sucess to define a ,but why it displays "caught WARNING" ? do i do > something wrong? Think about the name "SETF". It assigns a value to something. This "something" should be something it has seen before, or something you have declared before it. CL-USER> (defparameter *a*) *A* CL-USER> (setf *a* "dave") "dave" CL-USER> *a* "dave" CL-USER> (let ((a nil)) (setf a "dave") a) "dave" CL-USER> ..this way, you can be sure that you are only working with things you have "declared that you want to exist". Take this for instance: CL-USER> (let ((a nil)) (setf a "dave") (setf *b* "huh?")) ; in: LAMBDA NIL ; (SETF *B* "huh?") ; ==> ; (SETQ *B* "huh?") ; ; caught WARNING: ; undefined variable: *B* ; ; caught WARNING: ; This variable is undefined: ; *B* ; ; compilation unit finished ; caught 2 WARNING conditions "huh?" CL-USER> *b* "huh?" Suddenly *B* has popped up in the global environment without you having declared that it should exist (there). ...messy... -- Lars Rune Nøstdal http://nostdal.org/ |
From: Nicolas N. <ne...@ma...> - 2008-03-24 08:37:29
|
勇勇 <zho...@ya...> writes: > ; compilation unit finished > ; caught 2 WARNING conditions > "dave" > CL-USER> > > it sucess to define a ,but why it displays "caught WARNING" ? do i do something wrong? "Catching a condition" is standard terminology. You might look at the corresponding sections in the Hyperspec or Kent Pitman's condition paper: http://www.nhplace.com/kent/Papers/Condition-Handling-2001.html Nicolas |
From: Lars R. N. <lar...@gm...> - 2008-03-23 11:33:29
|
On Fri, 21 Mar 2008 19:30:28 +0000, Jeffrey Straszheim wrote: > Hello, Hi > I've recently decided to learn Lisp and have decided to start with SBCL, > as it was the only open source/free version I found that supports both > native compilation and real OS threads. However, I see that I'll have > to set up a Linux box to have access to the threading. > > It has been a few years since I did any Linux work and am sadly behind > the times on what distributions are good. What I'm hoping is someone on > this list can suggest a distribution that will provide the minimum pain > in getting SBCL up and working with threading. > > I don't need a "dumbed down" version: I'm comfortable with C and > makefiles and all of that. However, my goal is to learn Lisp, not screw > around with Linux, so the more straightforward the better. I'd recommend Ubuntu. The "boring stuff"(#1) is taken care of for you, but it's not "dumbed down" and you have access to everything you need to do development work. I would not recommend using/installing any of the Lisp stuff that "comes with" any of the distros though. That has only lead to trouble and hassle for me. I instead install SBCL and Lisp libraries "manually" in my home folder. This is a rough write-up of how I get up and running: http://common-lisp.net/~lnostdal/writings/sbcl.html > Thanks in advance > > Jeffrey Straszheim > > P.S. What is quickest way to get an HTTP application server up and > running on SBCL? I run a couple of small sites using Hunchentoot. It works great and is surely more comfortable using than, say, PHP. I've set it up behind Lighttpd so it redirect requests based on host to separate SBCL cores each running its own version of Hunchentoot + a web app (site). Another use for this, if the traffic increases, is to spread the load of a single site to many SBCL cores (copies of the same core file) each running on different machines. #1: sound card drivers, gfx card drivers, network driver, wireless driver, etc.etc. .. these things _usually_ "just work" in Ubuntu -- Lars Rune Nøstdal http://nostdal.org/ |
From: 勇勇 <zho...@ya...> - 2008-03-23 00:40:56
|
hi,everyone: i am new to sbcl and lisp! when i use "setq" to define something in emacs(slime+sbcl) SLIME 2006-04-20 CL-USER> (setq a "dave") ; in: LAMBDA NIL ; (SETQ A "dave") ; ; caught WARNING: ; undefined variable: A ; ; caught WARNING: ; This variable is undefined: ; A ; ; compilation unit finished ; caught 2 WARNING conditions "dave" CL-USER> it sucess to define a ,but why it displays "caught WARNING" ? do i do something wrong? --------------------------------- 雅虎邮箱传递新年祝福,个性贺卡送亲朋! |
From: Roman B. <ro...@bu...> - 2008-03-22 23:13:40
|
Hi, I am trying to figure out the magic that happens when I call sb- ext:save-lisp-and-die. I just started using sbcl. In a virgin image call to: (require :asdf) succeeds. In a saved image, run through --core argument, it fails. Thanks, Roman |
From: Matt R. <mre...@gm...> - 2008-03-21 20:07:56
|
Second using a binary to build the latest from source. I use Ubuntu (server), but any should work. I've used Hunchentoot for several low-traffic sites and have no complaints. I believe there's a port of AllegroServe for SBCL that some claim offers better perfromance. On Mar 21, 2008, at 3:36 PM, Brian Mastenbrook <br...@ma...> wrote: > Jeffrey Straszheim wrote: >> Hello, >> >> I've recently decided to learn Lisp and have decided to start with >> SBCL, as it >> was the only open source/free version I found that supports both >> native >> compilation and real OS threads. However, I see that I'll have to >> set up a >> Linux box to have access to the threading. >> >> It has been a few years since I did any Linux work and am sadly >> behind the times >> on what distributions are good. What I'm hoping is someone on this >> list can >> suggest a distribution that will provide the minimum pain in >> getting SBCL up and >> working with threading. >> >> I don't need a "dumbed down" version: I'm comfortable with C and >> makefiles and >> all of that. However, my goal is to learn Lisp, not screw around >> with Linux, so >> the more straightforward the better. >> >> Thanks in advance >> >> Jeffrey Straszheim >> >> P.S. What is quickest way to get an HTTP application server up and >> running on >> SBCL? > > These days nearly anything should work. I'm using OpenSUSE 10.3 on my > desktop and Debian stable (er, oldstable but upgrading soon) on my > server. If you've got 64-bit capable hardware, you may want to look > into > a 64-bit distribution. Alternately, modern AMD and Intel processors > can > virtualize a 64-bit OS under a 32-bit host. > > I would recommend staying away from distribution packages for SBCL. > Just > download the latest binary from the web site, install it, and use it > to > compile the latest sources. It's relatively straightforward; the only > thing that's even moderately tricky is building with threads. To do > that, create a file named "customize-target-features.lisp" in the root > of the SBCL sources containing something like: > > (lambda (list) (cons :sb-thread list)) > > Then just build SBCL as usual ("sh make.sh"). > > I'll let others answer the HTTP question as my views seem to be out of > the mainstream these days... > > -- > Brian Mastenbrook > br...@ma... > http://brian.mastenbrook.net/ > > --- > ---------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Sbcl-help mailing list > Sbc...@li... > https://lists.sourceforge.net/lists/listinfo/sbcl-help |
From: Brian M. <br...@ma...> - 2008-03-21 19:36:34
|
Jeffrey Straszheim wrote: > Hello, > > I've recently decided to learn Lisp and have decided to start with SBCL, as it > was the only open source/free version I found that supports both native > compilation and real OS threads. However, I see that I'll have to set up a > Linux box to have access to the threading. > > It has been a few years since I did any Linux work and am sadly behind the times > on what distributions are good. What I'm hoping is someone on this list can > suggest a distribution that will provide the minimum pain in getting SBCL up and > working with threading. > > I don't need a "dumbed down" version: I'm comfortable with C and makefiles and > all of that. However, my goal is to learn Lisp, not screw around with Linux, so > the more straightforward the better. > > Thanks in advance > > Jeffrey Straszheim > > P.S. What is quickest way to get an HTTP application server up and running on > SBCL? These days nearly anything should work. I'm using OpenSUSE 10.3 on my desktop and Debian stable (er, oldstable but upgrading soon) on my server. If you've got 64-bit capable hardware, you may want to look into a 64-bit distribution. Alternately, modern AMD and Intel processors can virtualize a 64-bit OS under a 32-bit host. I would recommend staying away from distribution packages for SBCL. Just download the latest binary from the web site, install it, and use it to compile the latest sources. It's relatively straightforward; the only thing that's even moderately tricky is building with threads. To do that, create a file named "customize-target-features.lisp" in the root of the SBCL sources containing something like: (lambda (list) (cons :sb-thread list)) Then just build SBCL as usual ("sh make.sh"). I'll let others answer the HTTP question as my views seem to be out of the mainstream these days... -- Brian Mastenbrook br...@ma... http://brian.mastenbrook.net/ |
From: <jst...@co...> - 2008-03-21 19:30:38
|
Hello, I've recently decided to learn Lisp and have decided to start with SBCL, as it was the only open source/free version I found that supports both native compilation and real OS threads. However, I see that I'll have to set up a Linux box to have access to the threading. It has been a few years since I did any Linux work and am sadly behind the times on what distributions are good. What I'm hoping is someone on this list can suggest a distribution that will provide the minimum pain in getting SBCL up and working with threading. I don't need a "dumbed down" version: I'm comfortable with C and makefiles and all of that. However, my goal is to learn Lisp, not screw around with Linux, so the more straightforward the better. Thanks in advance Jeffrey Straszheim P.S. What is quickest way to get an HTTP application server up and running on SBCL? |
From: Florian W. <fw...@de...> - 2008-03-15 23:32:29
|
* Russell McManus: > "Nikodemus Siivola" <nik...@ra...> writes: > >> I *think* that with sufficient linker magic you should be able to >> produce a .so that exports all symbols from your .a. I think. > > How can this work if the code in the library was not compiled -fPIC? The dynamic linker can perform relocations on some architectures. 8-) |
From: Russell M. <rus...@ya...> - 2008-03-15 21:06:56
|
"Nikodemus Siivola" <nik...@ra...> writes: > I *think* that with sufficient linker magic you should be able to > produce a .so that exports all symbols from your .a. I think. How can this work if the code in the library was not compiled -fPIC? -russ |