armedbear-ticket June 2016

armedbear-ticket@common-lisp.net

1 participants
7 discussions

[Armedbear-ticket] [armedbear] #383: Build standalone JARs which contain additional application code
by armedbear 13 Feb '19

13 Feb '19

#383: Build standalone JARs which contain additional application code -------------------------+----------------------- Reporter: mevenson | Owner: Type: enhancement | Status: new Priority: major | Milestone: 1.4.0 Component: other | Version: 1.4.0-dev Keywords: | -------------------------+----------------------- Clojure ("lein uberjar") as well as jruby ("warbler jar") have facilities for creating a standalone JAR which contains the runtime plus application. Other than creating the necessary assembly instructions, the only substantial problem would seem to be the need to further abstract the mechanism for finding ABCL-CONTRIB to something that could work on a pathname as well as an entire JAR. -- Ticket URL: <http://abcl.org/trac/ticket/383> armedbear <http://abcl.org> armedbear

1 1

[Armedbear-ticket] [armedbear] #384: Binary release has no invocation wrapper
by armedbear 15 Jun '17

15 Jun '17

#384: Binary release has no invocation wrapper ----------------------+----------------------- Reporter: mevenson | Owner: Type: defect | Status: new Priority: major | Milestone: 1.4.0 Component: other | Version: 1.4.0-dev Keywords: | ----------------------+----------------------- ABCL binary release should contain an invocation wrapper ('abcl{,.bat}'). -- Ticket URL: <http://abcl.org/trac/ticket/384> armedbear <http://abcl.org> armedbear

1 1

[armedbear] #391: "bad place for a wild pathname" on EXT:PROBE-DIRECTORY for NAME containing #\*
by armedbear 18 Apr '17

18 Apr '17

#391: "bad place for a wild pathname" on EXT:PROBE-DIRECTORY for NAME containing #\* -----------------------------------------------+------------------------ Reporter: mevenson | Owner: Type: defect | Status: new Priority: major | Milestone: 1.3.3 Component: interpreter | Version: Keywords: cl:probe-file ext:probe-directory | Parent Tickets: -----------------------------------------------+------------------------ John Pallister on #abcl reported problems with configuring ASDF via {{{ (asdf:initialize-source-registry '(:source-registry (:tree (:home "src/synchromesh")) :inherit-configuration))}}} for which he later traced down to problems with a pathname NAME containing a #\* character: {{{ <synchromesh> Ooh, that's interesting - EXTENSIONS:PROBE-DIRECTORY has found a filename in the specified directory tree that contains a "*". <synchromesh> Then (much deeper) org.armedbear.lisp.probe_file$pf_probe_directory.execute(probe_file.java:88) throws the error. }}} The exact error cases here still needs to be determined. TBD: What does it mean to PROBE-{DIRECTORY,FILE} on a PATHNAME containing #\*? -- Ticket URL: <http://abcl.org/trac/ticket/391> armedbear <http://abcl.org> armedbear

1 6

[armedbear] #402: Start publishing abcl binary maven artifacts
by armedbear 19 Nov '16

19 Nov '16

#402: Start publishing abcl binary maven artifacts ----------------------+---------------------------- Reporter: mevenson | Owner: Type: defect | Status: new Priority: major | Milestone: 1.3.4 Component: other | Version: 1.4.0-dev Keywords: | Parent Tickets: ----------------------+---------------------------- We should figure out how to get the abcl binary artifacts back into the public Maven repository system -- Ticket URL: <http://abcl.org/trac/ticket/402> armedbear <http://abcl.org> armedbear

1 2

[armedbear] #390: ABCL-ASDF:RESOLVE not working
by armedbear 17 Nov '16

17 Nov '16

#390: ABCL-ASDF:RESOLVE not working --------------------------+---------------------------- Reporter: mevenson | Owner: Type: defect | Status: new Priority: critical | Milestone: 1.4.0 Component: abcl-contrib | Version: 1.4.0-dev Keywords: abcl-asdf | Parent Tickets: --------------------------+---------------------------- Without the presence of a <file:~/.m2/> directory, populated by command line mvn usage, the ABCL-ASDF mechanism is not working: {{{ CL-USER> (ABCL-ASDF:RESOLVE-DEPENDENCIES "net.java.dev.jna" "jna" :VERSION "4.1.0") }}} {{{ Java exception 'org.eclipse.aether.collection.DependencyCollectionException: Failed to read artifact descriptor for net.java.dev.jna:jna:jar:4.1.0'. [Condition of type JAVA-EXCEPTION] 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: [RETRY] Retry ASDF operation. 3: [CLEAR-CONFIGURATION-AND-RETRY] Retry ASDF operation after resetting the configuration. 4: [RETRY] Retry SLIME REPL evaluation request. 5: [*ABORT] Return to SLIME's top level. }}} Switching between Maven versions 3.2.5 and 3.3.3 seems to give the same problems. -- Ticket URL: <http://abcl.org/trac/ticket/390> armedbear <http://abcl.org> armedbear

1 6

[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] #412: Using FASLs from a Jar
by armedbear 13 Jun '16

13 Jun '16

#412: Using FASLs from a Jar ----------------------+---------------------- Reporter: mevenson | Owner: Type: defect | Status: new Priority: major | Milestone: Component: (A)MOP | Version: Keywords: | Parent Tickets: ----------------------+---------------------- Vibhu notes in <http://article.gmane.org/gmane.lisp.armedbear.devel/3600> that he is unable to use FASLs from a Jar {{{ I've got #'asdf-jar:package to create a jar file containing lisp sources and fasls. With abcl-1.0.1, (asdf:operate 'asdf:load-op ...) uses the fasls from the jar, whereas with abcl-1.1.0 onwards those fasls are ignored and the jarred sources are compiled into ~/.cache/... again. Is this a bug, or is it a feature (as easyE seems to think it is, in the last two sentences at: http://stackoverflow.com/questions/4763910/abcl-compilation-and-primitives )? If it's a bug, here is how far I've got in my diagnosis. (asdf-jar:add-to-asdf "wispym.jar") shows this in abcl-1.0.1 ((#P"jar:file:/Users/vibhu/t3/wispym-all.jar!/**/*.*" T) (#P"jar:file:/Users/vibhu/t3/wispym-all.jar!/**/*.*" #P"jar:file:/Users/vibhu/t3/wispym-all.jar!/**/*.*") (#P"/Users/vibhu/.cache/common- lisp/abcl-1.0.1-svn-13750-13751-fasl38-solaris-x86/**/*.*" T) (#P"/___jar___file___root___/**/*.*" #P"/Users/vibhu/.cache/common- lisp/abcl-1.0.1-svn-13750-13751-fasl38-solaris-x86/**/*.*") (#P"jar:file:/**/*.jar!/**/*.*" #<TRANSLATE-JAR-PATHNAME {2B63F8AD}>) (T #P"/Users/vibhu/.cache/common- lisp/abcl-1.0.1-svn-13750-13751-fasl38-solaris-x86/**/*.*")) but this in abcl-1.3.2, ((#P"/**/*.*" T) (#P"/**/*.*" #P"/**/*.*") (#P"/Users/vibhu/.cache/common-lisp/abcl-1.3.2-fasl42-macosx-x64/**/*.*" T) (#P"/___jar___file___root___/**/*.*" #P"/Users/vibhu/.cache/common-lisp/abcl-1.3.2-fasl42-macosx-x64/**/*.*") (#P"jar:file:/**/*.jar!/**/*.*" #<TRANSLATE-JAR-PATHNAME {4F340027}>) (T #P"/Users/vibhu/.cache/common-lisp/abcl-1.3.2-fasl42-macosx-x64/**/*.*")) I think these are asdf output-translations, each specifying a source directory and a corresponding destination directory. The first two entries are significantly different between abcl-1.0.1 and abcl-1.3.2. ---- The reason I'd like to use the jarred fasls is that I'm distributing my program to customers. I don't want to spew fasls around their hard disks. I also don't want to get into having to explain to them to clear caches. (I do have to do this locally on occasion, e.g. when timestamps on files confuse the cache). But most importantly, I've got a large cl-yacc grammar that takes ages to macroexpand and compile. I don't want them to wait so long even though it's just on the first load. }}} -- Ticket URL: <http://abcl.org/trac/ticket/412> armedbear <http://abcl.org> armedbear

1 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-ticket June 2016