armedbear-ticket June 2014

armedbear-ticket@common-lisp.net

1 participants
4 discussions

[Armedbear-ticket] [armedbear] #355: cl+ssl/drakma fails on https requests
by armedbear 17 Nov '16

17 Nov '16

#355: cl+ssl/drakma fails on https requests ---------------------+----------------- Reporter: charmon | Owner: Type: defect | Status: new Priority: major | Milestone: Component: (A)MOP | Version: Keywords: | ---------------------+----------------- The following shows what happens if you try to fetch a URL using DRAKMA and https: CL-USER> (ql:quickload 'cl+ssl) To load "cl+ssl": Load 1 ASDF system: cl+ssl ; Loading "cl+ssl" ......... 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. . ARTIFACT_RESOLVING net.java.dev.jna:jna:pom:4.0.0 ARTIFACT_RESOLVED net.java.dev.jna:jna:pom:4.0.0 (/Users/sly/.m2/repository/net/java/dev/jna/jna/4.0.0/jna-4.0.0.pom) @ central (http://repo1.maven.org/maven2/, releases+snapshots) ARTIFACT_RESOLVING net.java.dev.jna:jna:jar:4.0.0 ARTIFACT_RESOLVED net.java.dev.jna:jna:jar:4.0.0 (/Users/sly/.m2/repository/net/java/dev/jna/jna/4.0.0/jna-4.0.0.jar) @ central (http://repo1.maven.org/maven2/, releases+snapshots) ... (CL+SSL) CL-USER> (ql:quickload 'drakma) To load "drakma": Load 1 ASDF system: drakma ; Loading "drakma" .... (DRAKMA) CL-USER> (drakma:http-request "https://www.google.com/") A failure in the SSL library occurred on handle #<com.sun.jna.Pointer native@0x7ffe7cc007f0 {6777A3D7}> (return code: 1). SSL error queue: error:140C5042:SSL routines:SSL_UNDEFINED_FUNCTION:called a function you should not call [Condition of type CL+SSL::SSL-ERROR-SSL] Restarts: 0: [RETRY] Retry SLIME REPL evaluation request. 1: [*ABORT] Return to SLIME's top level. 2: [ABORT] Abort thread. Backtrace: 0: (#<FUNCTION {4026A35B}> #<CL+SSL::SSL-ERROR-SSL {306F7D00}> #<FUNCTION {4026A35B}>) 1: (APPLY #<FUNCTION {4026A35B}> (#<CL+SSL::SSL-ERROR-SSL {306F7D00}> #<FUNCTION {4026A35B}>)) 2: (SYSTEM::RUN-HOOK SYSTEM::*INVOKE-DEBUGGER-HOOK* #<CL+SSL::SSL-ERROR- SSL {306F7D00}> #<FUNCTION {4026A35B}>) 3: (INVOKE-DEBUGGER #<CL+SSL::SSL-ERROR-SSL {306F7D00}>) 4: (ERROR CL+SSL::SSL-ERROR-SSL :HANDLE #<com.sun.jna.Pointer native@0x7ffe7cc007f0 {6777A3D7}> :RET 1 ...) 5: (#<FUNCTION {28AECC44}> (#<CL+SSL::SSL-STREAM {6BE49939}>)) 6: (#<FUNCTION {6D07A485}> (#<CL+SSL::SSL-STREAM {6BE49939}>)) 7: (GRAY-STREAMS:STREAM-FINISH-OUTPUT #<CL+SSL::SSL-STREAM {6BE49939}>) 8: (SYSTEM::%FINISH-OUTPUT #<CL+SSL::SSL-STREAM {6BE49939}>) 9: (FINISH-OUTPUT #<CL+SSL::SSL-STREAM {6BE49939}>) 10: (#<FUNCTION (LAMBDA (CL+SSL::CALLBACK-ARG-BIO- CL+SSL::CALLBACK-ARG- BUF- CL+SSL::CALLBACK-ARG-N-)) {10C24FAF}> #<com.sun.jna.Pointer native@0x7ffe7cb929c0 {44FD72C1}> #<com.sun.jna.Pointer native@0x7f.. 11: (JCALL #<java.lang.reflect.Method public java.lang.Object com.sun..... {6008072D}> #<com.sun.jna.Function native function SSL_connect(<pro.... {2F0F4C9C}> #<java.lang.Class class java.lang.Integer {15.. 12: (CL+SSL::SSL-CONNECT #<com.sun.jna.Pointer native@0x7ffe7cc007f0 {6777A3D7}>) 13: (CL+SSL:MAKE-SSL-CLIENT-STREAM #<TWO-WAY-STREAM {7FB606A}> :CLOSE- CALLBACK #<FUNCTION {876D33E}> :CERTIFICATE NIL ...) 14: (DRAKMA::MAKE-SSL-STREAM #<TWO-WAY-STREAM {7FB606A}> :CERTIFICATE NIL :KEY NIL ...) 15: (DRAKMA:HTTP-REQUEST "https://www.google.com/") 16: (SYSTEM::%EVAL (DRAKMA:HTTP-REQUEST "https://www.google.com/")) 17: (EVAL (DRAKMA:HTTP-REQUEST "https://www.google.com/")) --more-- I'm not sure if this is an ABCL problem, a DRAKMA problem, a CFFI problem, or a CL+SSL problem, but my guess is it's a ABCL problem. -- Ticket URL: <http://abcl.org/trac/ticket/355> armedbear <http://abcl.org> armedbear

1 1

[Armedbear-ticket] [armedbear] #360: Unable to load hunchentoot via quicklisp (maven, asdf problem?)
by armedbear 05 Jan '15

05 Jan '15

#360: Unable to load hunchentoot via quicklisp (maven, asdf problem?) ----------------------------+----------------- Reporter: david creelman | Owner: Type: defect | Status: new Priority: major | Milestone: Component: other | Version: Keywords: | ----------------------------+----------------- After successfully setting up quicklisp, I try to do :- (ql:quickload "hunchentoot") and get the following (apologies for bad formatting, copying from a Windows cmd window. ..... [package jss]..................................... [package abcl-asdf]............................... [package abcl-asdf-test]. ; in (EVAL-WHEN (:COMPILE-TOPLEVEL :LOAD-TOPLEVEL ...) ...) ; Caught SIMPLE-WARNING: ; Unable to locate Maven executable to find Maven Aether adaptors. jnaASDF could not load because The file http://repo1.maven.org/maven2/net/java/ dev/jna/jna/4.1.0/jna-4.1.0.jar does not exist.. #<THREAD "interpreter" {938BE3}>: Debugger invoked on condition of type FILE-ERR OR The file http://repo1.maven.org/maven2/net/java/dev/jna/jna/4.1.0/jna-4.1.0.ja r does not exist. Restarts: 0: RETRY Retry loading #<ASDF/INTERFACE:MVN "jna" "net.java.dev.jna/jna/4. 1.0">. 1: ACCEPT Continue, treating loading #<ASDF/INTERFACE:MVN "jna" "net.java.d ev.jna/jna/4.1.0"> as having been successful. 2: RETRY Retry compiling #<ASDF/LISP-ACTION:CL-SOURCE-FILE "cffi" "src" "c ffi-abcl">. 3: ACCEPT Continue, treating compiling #<ASDF/LISP-ACTION:CL-SOURCE- FILE "c ffi" "src" "cffi-abcl"> as having been successful. 4: ABORT Give up on "hunchentoot" 5: TOP-LEVEL Return to top level. [1] CL-USER(5): 0 jnaASDF could not load because The file http://repo1.maven.org/maven2/net/java/ dev/jna/jna/4.1.0/jna-4.1.0.jar does not exist.. #<THREAD "interpreter" {938BE3}>: Debugger invoked on condition of type FILE-ERR OR The file http://repo1.maven.org/maven2/net/java/dev/jna/jna/4.1.0/jna-4.1.0.ja r does not exist. Restarts: 0: RETRY Retry loading #<ASDF/INTERFACE:MVN "jna" "net.java.dev.jna/jna/4. 1.0">. 1: ACCEPT Continue, treating loading #<ASDF/INTERFACE:MVN "jna" "net.java.d ev.jna/jna/4.1.0"> as having been successful. 2: RETRY Retry compiling #<ASDF/LISP-ACTION:CL-SOURCE-FILE "cffi" "src" "c ffi-abcl">. 3: ACCEPT Continue, treating compiling #<ASDF/LISP-ACTION:CL-SOURCE- FILE "c ffi" "src" "cffi-abcl"> as having been successful. 4: ABORT Give up on "hunchentoot" 5: TOP-LEVEL Return to top level. Please let me know if you would like more information. This may be strictly speaking a quicklisp issue, but it seems to be calling in the ABCL asdf stuff. Regards, David -- Ticket URL: <http://abcl.org/trac/ticket/360> armedbear <http://abcl.org> armedbear

1 22

[Armedbear-ticket] [armedbear] #361: compile function fails
by armedbear 20 Jun '14

20 Jun '14

#361: compile function fails -----------------------------+----------------- Reporter: mariano montone | Owner: Type: defect | Status: new Priority: major | Milestone: Component: compiler | Version: Keywords: | -----------------------------+----------------- http://clhs.lisp.se/Body/f_cmp.htm fails in the latest ABCL version: 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" -- Ticket URL: <http://abcl.org/trac/ticket/361> armedbear <http://abcl.org> armedbear

1 3

Re: [Armedbear-ticket] [armedbear] #16: Re-evaluation of DEFPACKAGE form is ignored
by armedbear 20 Jun '14

20 Jun '14

#16: Re-evaluation of DEFPACKAGE form is ignored --------------------------+------------------------- Reporter: mevenson | Owner: somebody Type: enhancement | Status: new Priority: minor | Milestone: unscheduled Component: other | Version: 1.0 Resolution: | Keywords: --------------------------+------------------------- Comment (by mariano montone): There's no need to restart to export a symbol. It is enough to eval (export <symbol>) from the package. See: http://osdir.com/ml/armedbear-devel/2012-04/msg00032.html But yes, this is annoying. -- Ticket URL: <http://abcl.org/trac/ticket/16#comment:3> armedbear <http://abcl.org> armedbear

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-ticket June 2014