August 2014 - armedbear-devel - mailman3.common-lisp.net

[armedbear-devel] Setup changes for cl-test-grid.cloud.efficito.com
by Erik Huelsmann 08 Apr '15

08 Apr '15

Hi Anton, Looking at some of the test grid failures for ABCL, I noticed some of the OpenGL packages failing due to being unable to locate LibGL.so. To resolve that, I ran: $ aptitude install libgl1-mesa-swx11 Then I noticed something wanted to require JSS, but didn't know how to, so I've added "(require :abcl-contrib)" to /home/testgrid/.abclrc. With these in place cl-glfw-opengl-core seems to load just fine. Any other libraries or measures I should take in order to be able to load (currently failing) systems? Bye, Erik.

3 3

[Armedbear-devel] (require 'jna) broken by 0030b89b2
by Cyrus Harmon 06 Mar '15

06 Mar '15

Commit 0030b89b2eb24b0b63b5f1ca4d4c9a7644eea02d breaks the maven JNA resolution: (sly@cyruss-mbp):~/src/abcl$ ./abcl Armed Bear Common Lisp 1.4.0-dev Java 1.7.0_51 Oracle Corporation Java HotSpot(TM) 64-Bit Server VM Low-level initialization completed in 0.351 seconds. Startup completed in 1.786 seconds. Loading /Users/sly/.abclrc completed in 9.51 seconds. Type ":help" for a list of available commands. CL-USER(1): (require 'abcl-contrib) Using probed value of abcl-contrib: '/Users/sly/src/abcl/dist/abcl-contrib.jar'. Added jar:file:/Users/sly/src/abcl/dist/abcl-contrib.jar!/quicklisp/ to ASDF. Added jar:file:/Users/sly/src/abcl/dist/abcl-contrib.jar!/mvn/ to ASDF. Added jar:file:/Users/sly/src/abcl/dist/abcl-contrib.jar!/jss/ to ASDF. Added jar:file:/Users/sly/src/abcl/dist/abcl-contrib.jar!/jfli/ to ASDF. Added jar:file:/Users/sly/src/abcl/dist/abcl-contrib.jar!/asdf-jar/ to ASDF. Added jar:file:/Users/sly/src/abcl/dist/abcl-contrib.jar!/asdf-install/ to ASDF. Added jar:file:/Users/sly/src/abcl/dist/abcl-contrib.jar!/abcl-asdf/ to ASDF. ("ABCL-CONTRIB") CL-USER(2): (require 'jna) ARTIFACT_RESOLVING net.java.dev.jna:jna:pom:4.1.0 ARTIFACT_RESOLVED net.java.dev.jna:jna:pom:4.1.0 (/Users/sly/.m2/repository/net/java/dev/jna/jna/4.1.0/jna-4.1.0.pom) @ central (http://repo1.maven.org/maven2/, releases+snapshots) jnaASDF could not load because Java exception 'java.lang.NullPointerException'.. #<THREAD "interpreter" {4323B3D5}>: Debugger invoked on condition of type JAVA-EXCEPTION Java exception 'java.lang.NullPointerException'. Restarts: 0: RETRY Retry compiling #<ASDF/INTERFACE:MVN "jna" "net.java.dev.jna/jna/4.1.0">. 1: ACCEPT Continue, treating compiling #<ASDF/INTERFACE:MVN "jna" "net.java.dev.jna/jna/4.1.0"> as having been successful. 2: TOP-LEVEL Return to top level. [1] CL-USER(3): [1] CL-USER(4): :bt 0: (SYSTEM:BACKTRACE) 1: (INVOKE-DEBUGGER #<JAVA-EXCEPTION java.lang.NullPointerException {1DA02950}>) 2: org.armedbear.lisp.Lisp.error(Lisp.java:382) 3: org.armedbear.lisp.Java$pf_jnew.execute(Java.java:581) 4: org.armedbear.lisp.Primitive.execute(Primitive.java:135) 5: (JNEW #<java class org.eclipse.aether.resolution.DependencyRequest> #<org.eclipse.aether.graph.DefaultDependencyNode net.java.dev.jna:jna:jar:4.1.0 (.... {60206C1}> #<null {6F096BFB}>) 6: (ABCL-ASDF:RESOLVE-DEPENDENCIES "net.java.dev.jna" "jna" "4.1.0") 7: (#<FUNCTION {28D8442C}> (#<ASDF/INTERFACE:MVN "jna" "net.java.dev.jna/jna/4.1.0">)) Any clues? thanks, Cyrus _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

4 5

[Armedbear-devel] Tail recursion
by Ralf Moeller 06 Mar '15

06 Mar '15

Hi all, ABCL does not seem to support tail call optimization right now. Are there any plans to provide this? Best regards, Ralf Moeller _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

4 5

[Armedbear-devel] Question about pipes
by Sistemas 27 Sep '14

27 Sep '14

Hi: I'm trying to start some processes and connect them using pipes with ABCL (like Unix shell pipes). I've reviewed the documentation but I haven't found anything. Are I missing something? If not, are there any plans of adding input, output and error parameters for run-program (like SBCL, CCL, etc.)? Greets and thanks in advance. Rafael J. Alcántara Pérez. -- +---------- | Departamento de Sistemas <sistemas(a)dedaloingenieros.com> | Teléfono fijo: 952 602 959 | Fax: 952 602 959 | Dirección: C/ Afligidos 2, 3º Derecha, 29015 Málaga | Dédalo Ingenieros, S.L.: http://www.dedaloingenieros.com/ | PGP: http://pgp.rediris.es:11371/pks/lookup?op=index&search=0x1899F325 +--------------------- _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

5 7

[Armedbear-devel] Bug: compile function doesn't work
by Mariano Montone 27 Sep '14

27 Sep '14

Hello, This function is not working in the latest ABCL version: http://clhs.lisp.se/Body/f_cmp.htm This is what I get when I try to evaluate the example in CLHS: (defun foo () "bar") => FOO (compile 'foo) Wrong number of arguments for #<FUNCTION {5236A94B}>. [Condition of type PROGRAM-ERROR] Restarts: 0: [RETRY] Retry SLIME REPL evaluation request. 1: [*ABORT] Return to SLIME's top level. 2: [ABORT] Abort thread. Backtrace: 0: (#<FUNCTION {752CC03}> #<PROGRAM-ERROR {600776A0}> #<FUNCTION {752CC03}>) 1: (APPLY #<FUNCTION {752CC03}> (#<PROGRAM-ERROR {600776A0}> #<FUNCTION {752CC03}>)) 2: (SYSTEM::RUN-HOOK SYSTEM::*INVOKE-DEBUGGER-HOOK* #<PROGRAM-ERROR {600776A0}> #<FUNCTION {752CC03}>) 3: (INVOKE-DEBUGGER #<PROGRAM-ERROR {600776A0}>) 4: org.armedbear.lisp.Lisp.error(Lisp.java:382) 5: org.armedbear.lisp.CompiledClosure.notImplemented(CompiledClosure.java:81) 6: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:212) 7: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:121) 8: org.armedbear.lisp.FuncallableStandardObject.execute(FuncallableStandardObject.java:117) 9: org.armedbear.lisp.Symbol.execute(Symbol.java:826) 10: org.armedbear.lisp.compiler_pass2_387.execute(compiler-pass2.lisp:7495) 11: org.armedbear.lisp.compiler_pass2_370.execute(compiler-pass2.lisp:7450) 12: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:98) 13: org.armedbear.lisp.Symbol.execute(Symbol.java:803) 14: org.armedbear.lisp.compiler_pass2_386.execute(compiler-pass2.lisp:7495) 15: org.armedbear.lisp.Symbol.execute(Symbol.java:838) 16: org.armedbear.lisp.compiler_pass2_388.execute(compiler-pass2.lisp:7519) 17: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:109) 18: org.armedbear.lisp.Symbol.execute(Symbol.java:814) 19: org.armedbear.lisp.compiler_pass2_392.execute(compiler-pass2.lisp:7589) 20: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:98) 21: org.armedbear.lisp.LispThread.execute(LispThread.java:814) 22: org.armedbear.lisp.Lisp.evalCall(Lisp.java:575) 23: org.armedbear.lisp.Lisp.eval(Lisp.java:540) 24: org.armedbear.lisp.Primitives$pf__eval.execute(Primitives.java:345) 25: (COMPILE FOO) I'm not using this directly, but some libraries like closer-mop, need compile to work. Fails here: CL-USER> (lisp-implementation-type) "Armed Bear Common Lisp" CL-USER> (lisp-implementation-version) "1.4.0-dev-svn-14713" "OpenJDK_64-Bit_Server_VM-Oracle_Corporation-1.7.0_55-b14" "amd64-Linux-3.5.0-17-generic" It seems to work in some cases on ABCL 1.3.1, though. CL-USER> (compile 'foo) FOO NIL NIL But something like this signals an error: CL-USER> (compile nil '(lambda (x) x)) ; Evaluation aborted on #<PROGRAM-ERROR {4C62C417}>. With the same error above. CL-USER> (lisp-implementation-version) "1.3.1" "OpenJDK_64-Bit_Server_VM-Oracle_Corporation-1.7.0_55-b14" "amd64-Linux-3.5.0-17-generic" I couldn't put this on the bugs tracker because I don't have permissions. Cheers, Mariano _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

2 3

[Armedbear-devel] [CfPart] International Lisp Conference 2014, August 15-17, Montreal
by Didier Verna 19 Aug '14

19 Aug '14

ILC 2014 - International Lisp Conference "Lisp on the Move" August 15-17 2014, Université de Montréal, Montréal, Canada Sponsored by the Association of Lisp Users In cooperation with: ACM SIGPLAN http://ilc2014.iro.umontreal.ca/ Latest News: * Registration is now open. See http://ilc2014.iro.umontreal.ca/registration.php * Invited speakers announced. Christian Queinnec, Ambrose Bonnaire-Sergeant, Stefan Monnier, Marc Battyani. Scope: Lisp is one of the greatest ideas from computer science and a major influence for almost all programming languages and for all sufficiently complex software applications. The International Lisp Conference is a forum for the discussion of Lisp and, in particular, the design, implementation and application of any of the Lisp dialects. We encourage everyone interested in Lisp to participate. This year's focus is directed towards integrated solutions, including mobile computing. The conference also provides slots for lightning talks, to be registered on-site every day. The full programme is available here: http://ilc2014.iro.umontreal.ca/program.php Important Dates: - July 14, 2014: Early registration deadline - August 15, 2014: Conference starts Organizing Committee: General Chair: Marc Feeley (Université de Montréal, Montréal, Canada) Programme Chair: Didier Verna (EPITA Research lab, Paris, France) Local chair: Marc Feeley (Université de Montréal, Montréal, Canada) Programme Committee: Charlotte Herzeel, IMEC, ExaScience Life Lab, Belgium Dave Herman, Mozilla Research, USA Greg Pfeil, Clozure Associates, USA Irène Anne Durand, LaBRI University of Bordeaux, France Jim Newton, Cadence Design Systems, France Kuroda Hisao, Mathematical Systems Inc., Japan Matthew Might, University of Utah, USA Nicolas Neuss, Friedrich Alexander Universitat, Germany Ralf Möller, TUHH, Germany Sam Tobin-Hochstadt, Northeastern University, USA William Byrd, University of Utah, USA Contact: ilc14-organizing-committee at alu.org For more information, see http://ilc2014.iro.umontreal.ca/ -- Resistance is futile. You will be jazzimilated. Lisp, Jazz, Aïkido: http://www.didierverna.info _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

1 0

[Armedbear-devel] Motion to delete asdf-install from ABCL's contrib
by Erik Huelsmann 19 Aug '14

19 Aug '14

Hi all, Relaying a motion by slyrus (Cyrus Harmon) from IRC: can we delete asdf-install from ABCL's contrib package? I think we can and should, given that we now have Quicklisp well supported, so hereby I'm relaying. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in. _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

2 1

[Armedbear-devel] ASDF-announce email list is live again
by Robert P. Goldman 19 Aug '14

19 Aug '14

Dear CL implementers and maintainers, I apologize for the mass spam, but I am sending this out in order to limit all further ASDF release spam. Hans Huebner has kindly raised the ASDF-announce(a)common-lisp.net mailing list from the dead. See http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/asdf-announce for more details. Please either sign your list up for ASDF-announce, or appoint someone in your maintenance community to subscribe. In return, I undertake to keep traffic to this mailing list to an absolute minimum. Indeed, for the moment, I will be turning on "emergency" moderation of all traffic, to enforce this. I plan to cease sending these mass emails upon ASDF releases, effective immediately, so please do monitor the announcement list. Best, Robert _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

1 0

[Armedbear-devel] ASDF errors in latest ABCL
by Cyrus Harmon 19 Aug '14

19 Aug '14

So, it’s quite possible I’m doing something wrong here, but I’m having a problem loading an ASDF file: Error (UNBOUND-SLOT) during printing: #<ASDF/FIND-SYSTEM:LOAD-SYSTEM-DEFINITION-ERROR {342BCE09}> [Condition of type ASDF/FIND-SYSTEM:LOAD-SYSTEM-DEFINITION-ERROR] Restarts: 0: [REINITIALIZE-SOURCE-REGISTRY-AND-RETRY] Retry finding system abcl-cdk after reinitializing the source-registry. 1: [RETRY] Retry SLIME REPL evaluation request. 2: [*ABORT] Return to SLIME's top level. 3: [ABORT] Abort thread. Backtrace: 0: (#<FUNCTION {776A693B}> #<ASDF/FIND-SYSTEM:LOAD-SYSTEM-DEFINITION-ERROR {342BCE09}> #<FUNCTION {776A693B}>) 1: (APPLY #<FUNCTION {776A693B}> (#<ASDF/FIND-SYSTEM:LOAD-SYSTEM-DEFINITION-ERROR {342BCE09}> #<FUNCTION {776A693B}>)) 2: (SYSTEM::RUN-HOOK SYSTEM::*INVOKE-DEBUGGER-HOOK* #<ASDF/FIND-SYSTEM:LOAD-SYSTEM-DEFINITION-ERROR {342BCE09}> #<FUNCTION {776A693B}>) 3: (INVOKE-DEBUGGER #<ASDF/FIND-SYSTEM:LOAD-SYSTEM-DEFINITION-ERROR {342BCE09}>) 4: (ERROR ASDF/FIND-SYSTEM:LOAD-SYSTEM-DEFINITION-ERROR :NAME "abcl-cdk" :PATHNAME #P"/Users/sly/projects/abcl-cdk/abcl-cdk.asd" ...) 5: (#<FUNCTION {6B22DDBC}> #<PROGRAM-ERROR {27E3CBA1}>) 6: (SIGNAL #<PROGRAM-ERROR {27E3CBA1}>) 7: (ERROR PROGRAM-ERROR :FORMAT-CONTROL "Invalid initarg ~S in call to ~S with arglist ~S." :FORMAT-ARGUMENTS (:REPOSITORY MAKE-INSTANCE (#<ASDF/INTERFACE:MVN {5C4DCB7C}> :NAME "org.openscience.cdk/cdk-b.. 8: (MOP::CHECK-INITARGS (#<STANDARD-GENERIC-FUNCTION {22978F81}> #<STANDARD-GENERIC-FUNCTION {513D2D11}>) (#<ASDF/INTERFACE:MVN {5C4DCB7C}> :NAME "org.openscience.cdk/cdk-bundle/1.5.6-SNAPSHOT" :PATHNAME.. 9: (#<FUNCTION {6B4F0153}> #<STANDARD-CLASS ASDF/INTERFACE:MVN {2A4AE9E8}> :NAME "org.openscience.cdk/cdk-bundle/1.5.6-SNAPSHOT" :PATHNAME NIL ...) 10: (APPLY #<FUNCTION {6B4F0153}> (#<STANDARD-CLASS ASDF/INTERFACE:MVN {2A4AE9E8}> :NAME "org.openscience.cdk/cdk-bundle/1.5.6-SNAPSHOT" :PATHNAME NIL :PARENT ...)) 11: (MAKE-INSTANCE #<STANDARD-CLASS ASDF/INTERFACE:MVN {2A4AE9E8}> :NAME "org.openscience.cdk/cdk-bundle/1.5.6-SNAPSHOT" :PATHNAME NIL ...) 12: (APPLY MAKE-INSTANCE #<STANDARD-CLASS ASDF/INTERFACE:MVN {2A4AE9E8}> (:NAME "org.openscience.cdk/cdk-bundle/1.5.6-SNAPSHOT" :PATHNAME NIL :PARENT #<ASDF/SYSTEM:SYSTEM {3E0B9897}> ...)) 13: (ASDF/PARSE-DEFSYSTEM:PARSE-COMPONENT-FORM #<ASDF/SYSTEM:SYSTEM {3E0B9897}> (:MVN "org.openscience.cdk/cdk-bundle/1.5.6-SNAPSHOT" :REPOSITORY NIL) :PREVIOUS-SERIAL-COMPONENT "org.freehep/freehep-graph.. 14: (ASDF/PARSE-DEFSYSTEM:PARSE-COMPONENT-FORM NIL (:MODULE "abcl-cdk" :PATHNAME NIL :NAME "abcl-cdk" ...)) 15: (#<FUNCTION {FE0272F}>) 16: (ASDF/CACHE:CALL-WITH-ASDF-CACHE #<FUNCTION {FE0272F}> :OVERRIDE NIL :KEY NIL) 17: (ASDF/PARSE-DEFSYSTEM:REGISTER-SYSTEM-DEFINITION :ABCL-CDK :NAME "abcl-cdk" :AUTHOR "Cyrus Harmon" ...) 18: (APPLY ASDF/PARSE-DEFSYSTEM:REGISTER-SYSTEM-DEFINITION :ABCL-CDK (:NAME "abcl-cdk" :AUTHOR "Cyrus Harmon" :SERIAL T ...)) 19: (SYSTEM::%LOAD #P"/Users/sly/projects/abcl-cdk/abcl-cdk.asd" NIL NIL T :UTF-8) --more-- So while it’s possible there may be an error in my ASDF file, it seems like we’re erroring out with a bogus error message. I’m having a hard time figuring out what the invalid initarg it’s complaining about in lines 7 and 8 are. Cyrus _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

2 1

[Armedbear-devel] [CfPart] International Lisp Conference 2014, August 15-17, Montreal
by Didier Verna 19 Aug '14

19 Aug '14

ILC 2014 - International Lisp Conference "Lisp on the Move" August 15-17 2014, Université de Montréal, Montréal, Canada Sponsored by the Association of Lisp Users In cooperation with: ACM SIGPLAN http://ilc2014.iro.umontreal.ca/ Latest News: * Only 4 days left before the early registration deadline! * Registration is now open. See http://ilc2014.iro.umontreal.ca/registration.php * Invited speakers announced. Christian Queinnec, Ambrose Bonnaire-Sergeant, Stefan Monnier, Marc Battyani. Scope: Lisp is one of the greatest ideas from computer science and a major influence for almost all programming languages and for all sufficiently complex software applications. The International Lisp Conference is a forum for the discussion of Lisp and, in particular, the design, implementation and application of any of the Lisp dialects. We encourage everyone interested in Lisp to participate. This year's focus is directed towards integrated solutions, including mobile computing. The conference also provides slots for lightning talks, to be registered on-site every day. The full programme is available here: http://ilc2014.iro.umontreal.ca/program.php Important Dates: - July 14, 2014: Early registration deadline - August 15, 2014: Conference starts Organizing Committee: General Chair: Marc Feeley (Université de Montréal, Montréal, Canada) Programme Chair: Didier Verna (EPITA Research lab, Paris, France) Local chair: Marc Feeley (Université de Montréal, Montréal, Canada) Programme Committee: Charlotte Herzeel, IMEC, ExaScience Life Lab, Belgium Dave Herman, Mozilla Research, USA Greg Pfeil, Clozure Associates, USA Irène Anne Durand, LaBRI University of Bordeaux, France Jim Newton, Cadence Design Systems, France Kuroda Hisao, Mathematical Systems Inc., Japan Matthew Might, University of Utah, USA Nicolas Neuss, Friedrich Alexander Universitat, Germany Ralf Möller, TUHH, Germany Sam Tobin-Hochstadt, Northeastern University, USA William Byrd, University of Utah, USA Contact: ilc14-organizing-committee at alu.org For more information, see http://ilc2014.iro.umontreal.ca/ -- Resistance is futile. You will be jazzimilated. Lisp, Jazz, Aïkido: http://www.didierverna.info _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

1 0