armedbear-devel

armedbear-devel@common-lisp.net

2 participants
1202 discussions

Re: problems in compiler
by Mark Evenson 30 Mar '19

30 Mar '19

[Posting reply to mailing list so our conversation gets archived for posterity.] > On Mar 30, 2019, at 05:10, Don Cohen <don-abcl(a)isis.cs3-inc.com> wrote: > > Mark Evenson writes: > >> It took a little while to approach the AP5 code, but I managed to >> hack together the attached patch for ABCL which allows the AP5 >> build strategy to succeed. […] >> The attached patch contains a provisional hack to the ABCL compiler >> which computes the alist form from the vector form rather than >> signalling an error, so in order to use ABCL with AP5, you will >> have to build ABCL from source. > > Thank you! > > But is there any reason it won't suffice to simply redefine this > function in a running image before compiling? Patching the compiler in the running image will work just fine. >> To truly fix this one would have to understand the AP5 compilation >> strategy better, and then probably adjust the compiler's use of >> specials. > > I think I understand the compilation strategy - it's not that > complicated. But I don't see what that has to do with this > problem. The patch suggests that the real question is how > *fasl-uninterned-symbols* got to be a vector in the first place. > Would it help if I avoided uninterned symbols? Replace calls to > gensym with gentemp? The reason I suspect AP5’s "compilation strategy” (more like “need for recompiling and loading as it goes”) is twofold: 1) In my attempt at reproduction of the problem, I encountered no problems with a toy fasl containing references to uninterned symbols with any combination of CL:LOAD and CL:COMPILE-FILE. Absence of evidence is not evidence of absence and all that, but the ABCL compiler works with many systems in Quicklisp defined using ASDF without problems. 2) From the stack trace, it seems clear that the error stems from the compiler being invoked (see ’59:’ ff.) in the process of the loading the fasl itself (’70:’ ff.): […] 57: (JVM::SERIALIZE-OBJECT (#:A77910 #:A77911)) 58: (JVM::EMIT-CONSTRUCTOR-LAMBDA-LIST (#:A77910 #:A77911)) 59: (COMPILE AP5::|Test-RELADDER| (LAMBDA (#:A77910 #:A77911) (AP5:WITHREADACCESS (LET ((#:G77912 #:A77910) (#:G77913 #:A77911)) (LET ((AP5::CXVALUE (AP5::VALUEINCURRENTCX (AP5:THEAP5RELATION AP5:RELADDER) #:G77912 #:G77913))) (COND ((NOT (EQ AP5::CXVALUE 'AP5::INHERIT)) AP5::CXVALUE) (T (NOT (NOT ((LAMBDA (AP5::REL &REST AP5::TUPLE) (AP5::FMEMB3 AP5::TUPLE (AP5::GETBASEDATA AP5::REL) )))))))))))) […] 64: (AP5::NEED-TESTER ) 65: (AP5::GET-UPDATE-SOURCE T ) 66: (AP5::GET-UPDATE T ) 67: (#<COMPILED-FUNCTION #<FUNCTION (LAMBDA ()) {6992BE4}> {6992BE4}>) 68: (FUNCALL #<COMPILED-FUNCTION #<FUNCTION (LAMBDA ()) {6992BE4}> {6992BE4}>) 69: (SYSTEM:INIT-FASL :VERSION 43) 70: (SYSTEM::%LOAD #P"/Users/evenson/work/ap5/bin-abcl1.5.0-MT/relation.fas" T NIL T :DEFAULT) 71: (LOAD #P"/Users/evenson/work/ap5/bin-abcl1.5.0-MT/relation.fas”) ABCL fasls are zip files that contain two things: a loader consisting of CL source forms, and JVM classes emitted by the compiler. In loading, the loader forms are interpreted which make the necessary modifications to the environment as well as loading the compiled JVM classes. Each JVM class emitted by the compiler has a piece of initialization code (known in the JVM as static initializers) which performs additional housekeeping in the environment. In the above stack trace, the INIT-FASL call at ’69:’ is evaluating the forms in the loader. The loading of the JVM class which is causing the stack trace which seemingly corresponds to the error is on line 392 of “relation.lsp”, namely the line which adds a tester: (++ RelTester 'StructProp ‘StructPropTester) But I can’t “seemingly" figure out how this line expands into the call to AP5::GETUPDATE, so maybe my reasoning is somehow faulty here, but I at least wanted to record how far I have gotten. The only strategy I can currently suggest for AP5 which might be friendlier to ABCL is to not invoke CL:COMPILE at fasl load time if this is indeed what is occuring. Maybe I can craft a simple example to test that theory. Off to pack and travel to the European Lisp Symposium, Mark -- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now."

2 1

problems in compiler
by don-abcl＠isis.cs3-inc.com 29 Mar '19

29 Mar '19

--text follows this line-- The version of ap5 from 2009 supposedly was able to build in the abcl of that time. I'm now trying to make a more recent ap5 (but not very much changed) build in current abcl. I've put the current source at http://ap5.com/ under ap5-2019.zip so that others who are willing to help can reproduce the problem. Unfortunately I don't have a small example, only a large one. If you retrieve and unzip the source, you'll find a file abcl-build.lsp which I'm trying to get to build ap5. In order to use it you have to change this line: (defvar *top* "/tmp1/ap5-2017/") to be the directory where you've put the ap5 source subdirectory. That is, the file /whatever/source/abcl-build.lsp should contain (defvar *top* "/whatever/") I then do the following: java -jar abcl-bin-1.5.0/abcl.jar then load that file - in my case (load "/tmp1/ap5-2017/source/abcl-build.lisp") This ends with the following error: Error loading /home/tmp1/ap5-2017/bin-abcl1.5.0-MT/relation.fas at line 210 (offset 12978) #<THREAD "interpreter" {5E5D5718}>: Debugger invoked on condition of type TYPE-ERROR The value #(#:A63056 #:G63088 #:A63337 #:A63338 #:A63324 #:A63325 #:G63450 #:G63451 #:A63559 #:A63560 #:A63546 #:A63547 #:G63674 #:G63675 #:A63797 #:A63798 #:G63898 #:G63899 #:A64007 #:A64008 #:G64039 #:G64040 #:A64134 #:G64160 #:G64256 #:G64356 #:G64357 #:G64454 #:A64602 #:G64628 #:WHOLE-65572 #:ENVIRONMENT-65573) is not of type LIST. Restarts: 0: TOP-LEVEL Return to top level. [1] AP5(2): :bt 0: (SYSTEM:BACKTRACE) 1: (INVOKE-DEBUGGER #<TYPE-ERROR {16575712}>) 2: org.armedbear.lisp.Lisp.error(Lisp.java:382) 3: org.armedbear.lisp.Lisp.type_error(Lisp.java:435) 4: org.armedbear.lisp.LispObject.car(LispObject.java:161) 5: org.armedbear.lisp.assql.execute(assql.java:51) 6: org.armedbear.lisp.Symbol.execute(Symbol.java:814) 7: org.armedbear.lisp.LispThread.execute(LispThread.java:832) [1] AP5(3): It's difficult for me to figure out what's causing the error since I don't know much about interpreting java compiler output. However I hope a little background and some experimental evidence will help. First, the build process loads certain files before it compiles them and then later attempts to load the compiled versions. The error is coming from trying to load the compiled version of the first of these, relations.lsp. The build process actually loads and compiles several files before it tries to load the compiled versions, but in order to reproduce the error it's enough to load relations.lsp, compile it, then try to load the compiled version. In order to figure out which form in the file was causing the problem I tried a number of initial subsets of the relations.lsp file and found that if I stop at line 836, after : (++ reldeleter (relationp 'relation) '(lambda (&rest ignore) (declare (ignore ignore)) 'deleterel)) I can - load relations.lsp (I do this in order to return to a state that does not depend on the part of the compiled file that was loaded) - compile the initial segment - load the compiled version of the initial segment without error. However if I add the next form, (defun deleterel (ignore rel) (declare (ignore ignore)) (loop for a s.t. (relationarity rel a) do (-- relationarity rel a)) (insist "supposed to delete it" not (relation rel))) the load of the compiled file generates an error similar to above: Error loading /tmp/test1.abcl at line 198 (offset 11994) #<THREAD "interpreter" {2040734F}>: Debugger invoked on condition of type TYPE-ERROR The value #(#:G292048) is not of type LIST. On the other hand, if I put the defun deleterel into a separate file, I can - load relations.lsp - compile the initial segment ending with ++ reldeleter - load the compiled version of the initial segment - compile the file containing defun deleterel - load that file without error. The fact that the error from this test contains what appears to be a vector of only one object whereas the original contains a longer vector suggests to me that the compiler is combining multiple forms into a vector, and the defun deleterel is just the first one. Of course that doesn't explain why some other code expects a list instead of a vector. I'm hoping that someone will know immediately what causes the error I'm seeing and what I can do to avoid it. This reminded me of something -- you might notice in the file relations.lsp and other files the following incantation: (buffer-break) which is defined in sys-depe.lsp: ; The purpose of buffer-break is to prevent compile-file from ; putting two forms together when the first one has to be evaluated ; before the second can successfully read, e.g., if the first defines ; relation R and the second contains something like #,(relationp R). #+(or lispworks (and lucid sparc)) (defmacro buffer-break () '(eval-when (:load-toplevel :execute) nil)) #-(or lispworks (and lucid sparc)) (defmacro buffer-break () nil) If I change the first of those forms to #+(or abcl lispworks (and lucid sparc)) I still get the same error at the same place, but I wonder whether the underlying problem is similar to the one that caused buffer-break to be invented.

2 1

ASDF 3.3.3 is Released
by Robert Goldman 27 Mar '19

27 Mar '19

In honor of the impending 2019 European Lisp Symposium, today we release ASDF 3.3.3, the third bugfix release for the 3.3 release series. We urge implementations that are currently bundling previous versions of ASDF -- and especially those bundling 3.3.0 or 3.3.1 -- to upgrade to 3.3.3 at their earliest convenience. Immense thanks, as always, to Faré Rideau. Also thanks to the many bug reporters and patch submitters including (alphabetically): * Marius Gerbershagen * Hugo Ishimaru * Attila Lendvai * Jan Moringen * P. Neidhardt * François-René Rideau * Eric Timmons * Didier Verna * "privet-kitty" The Changelog: ``` Bug fix release: * Dependency tracking: fix bugs in handling misnamed secondary systems. We now distinguish between "syntactic" and "semantic" primariness, properly warn in case a secondary system is misnamed, yet properly recompile or avoid spurious recompilation depending on whether there or not is a conflict or redefinition. Similarly handle package-inferred-system (thanks to Eric Timmons). Better warning in a fishy case of compute-action-stamp. * UIOP: Fix loading, allow the user to specify UIOP location from which to load. * SBCL compatibility: Fix issue with deferred warnings on SBCL. * Allegro compatibility: Fix issue detecting "modern" lisp. * Genera compatibility: Fix minor issues. Not fully tested. * ECL compatibility: Bundling fixes. * Fiveam-ASDF: Added to contrib/ example system for integrating FiveAM tests with ASDF's test-op. * Miscellaneous fixes: Avoid an infinite loop parsing :perform options, quash warnings for known bad system names that won't be fixed. * Documentation: Multiple user-contributed documentation fixes. * Tests: Miscellaneous improvements. -- Francois-Rene Rideau <fare(a)tunes.org> Wed, 27 Mar 2019 17:33:42 -0400 ```

1 0

user manual code example race condition
by dingd 17 Mar '19

17 Mar '19

this is recommended in the manual, it contains a race condition. Interpreter interpreter = Interpreter.getInstance (); if ( interpreter == null ) { interpreter = Interpreter.createInstance (); } getInstance and createInstance should be swapped.

5 10

cffi doesn't load on ABCl 1.5 and 1.4 (but works on 1.3 and odler)
by Anton Vodonosov 08 Mar '19

08 Mar '19

1.5 fails with NullPointerException 1.4 with org.armedbear.lisp.Go Best regards, - Anton (ql:quickload :cffi) Java exception 'java.lang.NullPointerException'. [Condition of type JAVA-EXCEPTION] Restarts: 0: [ABORT] Abort thread. Backtrace: 0: (#<FUNCTION {9B7F44}> #<JAVA-EXCEPTION {4A3C4C}> #<FUNCTION {9B7F44}>) 1: (APPLY #<FUNCTION {9B7F44}> (#<JAVA-EXCEPTION {4A3C4C}> #<FUNCTION {9B7F44}>)) 2: (SYSTEM::RUN-HOOK SYSTEM::*INVOKE-DEBUGGER-HOOK* #<JAVA-EXCEPTION {4A3C4C}> #<FUNCTION {9B7F44}$ 3: (INVOKE-DEBUGGER #<JAVA-EXCEPTION {4A3C4C}>) 4: org.armedbear.lisp.Lisp.error(Lisp.java:382) 5: org.armedbear.lisp.Java.jcall(Java.java:911) 6: org.armedbear.lisp.Java$pf_jcall.execute(Java.java:755) 7: org.armedbear.lisp.Primitive.execute(Primitive.java:123) 8: (JCALL "toString" NIL) 9: (SYSTEM::TO-FILE #S(SYSTEM::SYSTEM-STREAM) NIL :APPEND NIL) 10: (#<FUNCTION {12471FB}>) 11: (THREADS::THREAD-FUNCTION-WRAPPER #<FUNCTION {12471FB}>)

2 4

simple hello world fails - can't find LISP_HOME
by Stephen Varey 17 Jan '19

17 Jan '19

I have built abcl from source Then went to write my first simple hello world.... public class Tester { void simple() { Interpreter interpreter = Interpreter.createInstance(); LispObject result = interpreter.eval("(format t \"Hello, world!~%\")"); System.out.println(result); } public static void main(String[] args) { new Tester().simple(); } } The execution fails with the following. ant -f C:\\git\\abcl -Djavac.includes=org/armedbear/lisp/util/Tester.java - Dnb.internal.action.name=run.single -Drun.class=org.armedbear.lisp.util.Tester run-single init: Deleting: C:\git\abcl\build\built-jar.properties deps-jar: Updating property file: C:\git\abcl\build\built-jar.properties Compiling 1 source file to C:\git\abcl\build\classes compile-single: run-single: LISP_HOME C:\git\abcl\src\org\armedbear\lisp\ java.lang.ClassNotFoundException: org.armedbear.lisp.SpecialOperators at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:264) at org.armedbear.lisp.Lisp.loadClass(Lisp.java:2791) at org.armedbear.lisp.Lisp.<clinit>(Lisp.java:2802) at org.armedbear.lisp.Function$pf_function_class_bytes.<init>(Function.java:225) at org.armedbear.lisp.Function.<clinit>(Function.java:222) at org.armedbear.lisp.Interpreter.<clinit>(Interpreter.java:532) at org.armedbear.lisp.util.Tester.simple(Tester.java:34) at org.armedbear.lisp.util.Tester.main(Tester.java:50) java.lang.ClassNotFoundException: org.armedbear.lisp.AutoloadGeneralizedReference at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:264) at org.armedbear.lisp.Lisp.loadClass(Lisp.java:2791) at org.armedbear.lisp.Lisp.<clinit>(Lisp.java:2807) at org.armedbear.lisp.Function$pf_function_class_bytes.<init>(Function.java:225) at org.armedbear.lisp.Function.<clinit>(Function.java:222) at org.armedbear.lisp.Interpreter.<clinit>(Interpreter.java:532) at org.armedbear.lisp.util.Tester.simple(Tester.java:34) at org.armedbear.lisp.util.Tester.main(Tester.java:50) java.lang.ClassNotFoundException: org.armedbear.lisp.cxr at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:264) at org.armedbear.lisp.Lisp.loadClass(Lisp.java:2791) at org.armedbear.lisp.Lisp.<clinit>(Lisp.java:2808) at org.armedbear.lisp.Function$pf_function_class_bytes.<init>(Function.java:225) at org.armedbear.lisp.Function.<clinit>(Function.java:222) at org.armedbear.lisp.Interpreter.<clinit>(Interpreter.java:532) at org.armedbear.lisp.util.Tester.simple(Tester.java:34) at org.armedbear.lisp.util.Tester.main(Tester.java:50) java.lang.ClassNotFoundException: org.armedbear.lisp.Do at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:264) at org.armedbear.lisp.Lisp.loadClass(Lisp.java:2791) at org.armedbear.lisp.Lisp.<clinit>(Lisp.java:2809) at org.armedbear.lisp.Function$pf_function_class_bytes.<init>(Function.java:225) at org.armedbear.lisp.Function.<clinit>(Function.java:222) at org.armedbear.lisp.Interpreter.<clinit>(Interpreter.java:532) at org.armedbear.lisp.util.Tester.simple(Tester.java:34) at org.armedbear.lisp.util.Tester.main(Tester.java:50) java.lang.ClassNotFoundException: org.armedbear.lisp.dolist at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:264) at org.armedbear.lisp.Lisp.loadClass(Lisp.java:2791) at org.armedbear.lisp.Lisp.<clinit>(Lisp.java:2810) at org.armedbear.lisp.Function$pf_function_class_bytes.<init>(Function.java:225) at org.armedbear.lisp.Function.<clinit>(Function.java:222) at org.armedbear.lisp.Interpreter.<clinit>(Interpreter.java:532) at org.armedbear.lisp.util.Tester.simple(Tester.java:34) at org.armedbear.lisp.util.Tester.main(Tester.java:50) java.lang.ClassNotFoundException: org.armedbear.lisp.dotimes at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:264) at org.armedbear.lisp.Lisp.loadClass(Lisp.java:2791) at org.armedbear.lisp.Lisp.<clinit>(Lisp.java:2811) at org.armedbear.lisp.Function$pf_function_class_bytes.<init>(Function.java:225) at org.armedbear.lisp.Function.<clinit>(Function.java:222) at org.armedbear.lisp.Interpreter.<clinit>(Interpreter.java:532) at org.armedbear.lisp.util.Tester.simple(Tester.java:34) at org.armedbear.lisp.util.Tester.main(Tester.java:50) java.lang.ClassNotFoundException: org.armedbear.lisp.ash at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:264) at org.armedbear.lisp.Lisp.loadClass(Lisp.java:2791) at org.armedbear.lisp.Lisp.<clinit>(Lisp.java:2816) at org.armedbear.lisp.Function$pf_function_class_bytes.<init>(Function.java:225) at org.armedbear.lisp.Function.<clinit>(Function.java:222) at org.armedbear.lisp.Interpreter.<clinit>(Interpreter.java:532) at org.armedbear.lisp.util.Tester.simple(Tester.java:34) at org.armedbear.lisp.util.Tester.main(Tester.java:50) java.lang.ClassNotFoundException: org.armedbear.lisp.PackageFunctions at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:264) at org.armedbear.lisp.Lisp.loadClass(Lisp.java:2791) at org.armedbear.lisp.Lisp.<clinit>(Lisp.java:2818) at org.armedbear.lisp.Function$pf_function_class_bytes.<init>(Function.java:225) at org.armedbear.lisp.Function.<clinit>(Function.java:222) at org.armedbear.lisp.Interpreter.<clinit>(Interpreter.java:532) at org.armedbear.lisp.util.Tester.simple(Tester.java:34) at org.armedbear.lisp.util.Tester.main(Tester.java:50) Unable to determine LISP_HOME. Unable to determine LISP_HOME. org.armedbear.lisp.IntegrityError ERROR placeholder called with arguments: at org.armedbear.lisp.Primitives$pf_error.execute(Primitives.java:1577) Failed to find loadable system file 'boot.lisp' in boot classpath. at org.armedbear.lisp.Primitive.execute(Primitive.java:113) at org.armedbear.lisp.Symbol.execute(Symbol.java:803) at org.armedbear.lisp.Lisp.error(Lisp.java:383) Failed to find loadable system file 'boot.lisp' in boot classpath. at org.armedbear.lisp.Load.loadSystemFile(Load.java:322) at org.armedbear.lisp.Interpreter.initializeLisp(Interpreter.java:172) at org.armedbear.lisp.Interpreter.createInstance(Interpreter.java:72) at org.armedbear.lisp.util.Tester.simple(Tester.java:34) at org.armedbear.lisp.util.Tester.main(Tester.java:50) Exception in thread "main" org.armedbear.lisp.IntegrityError at org.armedbear.lisp.Primitives$pf_error.execute(Primitives.java:1577) at org.armedbear.lisp.Primitive.execute(Primitive.java:113) at org.armedbear.lisp.Symbol.execute(Symbol.java:803) at org.armedbear.lisp.Lisp.error(Lisp.java:383) at org.armedbear.lisp.Load.loadSystemFile(Load.java:322) at org.armedbear.lisp.Interpreter.initializeLisp(Interpreter.java:172) at org.armedbear.lisp.Interpreter.createInstance(Interpreter.java:72) at org.armedbear.lisp.util.Tester.simple(Tester.java:34) at org.armedbear.lisp.util.Tester.main(Tester.java:50) C:\git\abcl\nbproject\build-impl.xml:1339: The following error occurred while executing this line: C:\git\abcl\nbproject\build-impl.xml:980: Java returned: 1 BUILD FAILED (total time: 0 seconds)

2 1

Resolved: ABCL doesn't current work beyond Java 8 (was Re: build failure)
by Mark Evenson 17 Jan '19

17 Jan '19

> > On Jan 15, 2019, at 16:14, Stephen Varey <srvarey(a)gmail.com> wrote: > > > > Hi > > > > I downloaded the source and built in netbeans where i get this error > > > > JAVA-EXCEPTION: Java exception 'java.lang.NoSuchMethodException: No applicable method named getURLs found in java.lang.ClassLoader or jdk.internal.loader.ClassLoaders$AppClassLoader'. > > C:\git\abcl\etc\ant\netbeans-build.xml:15: The following error occurred while executing this line: > > C:\git\abcl\build.xml:280: The following error occurred while executing this line: > > C:\git\abcl\build.xml:299: Java returned: -1 > > BUILD FAILED (total time: 13 seconds) > > > > Can you help? > > > > Thanks > > stephen > > > On Jan 16, 2019, at 10:23, Stephen Varey <srvarey(a)gmail.com> wrote: > > Hi > Thanks for replying > I just this minute found a thread saying there was a problem with java 10 - which is the default for netbeans. > Just finished compiling with java 8 and that was ok That the ABCL build mechanism doesn’t emit a meaningful diagnostic (or better works beyond Java 8) has been [filed as a ticket][1]. [1]: https://abcl.org/trac/ticket/46 -- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now."

1 0

Re: armedbear-devel Digest, Vol 52, Issue 2
by Stephen Varey 16 Jan '19

16 Jan '19

I have joined the mailing list as requested if you could just help me with this last thing I would so appreciated it I can build now - so thats ok just my hello world give this error ant -f C:\\git\\abcl -Djavac.includes=org/armedbear/lisp/util/Tester.java - Dnb.internal.action.name=run.single -Drun.class=org.armedbear.lisp.util.Tester run-single init: Deleting: C:\git\abcl\build\built-jar.properties deps-jar: Updating property file: C:\git\abcl\build\built-jar.properties Compiling 1 source file to C:\git\abcl\build\classes compile-single: run-single: Hello java.lang.ClassNotFoundException: org.armedbear.lisp.SpecialOperators java.lang.ClassNotFoundException: org.armedbear.lisp.AutoloadGeneralizedReference java.lang.ClassNotFoundException: org.armedbear.lisp.cxr java.lang.ClassNotFoundException: org.armedbear.lisp.Do java.lang.ClassNotFoundException: org.armedbear.lisp.dolist java.lang.ClassNotFoundException: org.armedbear.lisp.dotimes java.lang.ClassNotFoundException: org.armedbear.lisp.ash java.lang.ClassNotFoundException: org.armedbear.lisp.PackageFunctions at org.armedbear.lisp.util.Tester.main(Tester.java:57) Unable to determine LISP_HOME. Unable to determine LISP_HOME. ERROR placeholder called with arguments: org.armedbear.lisp.IntegrityError at org.armedbear.lisp.util.Tester.main(Tester.java:57) C:\git\abcl\nbproject\build-impl.xml:1339: The following error occurred while executing this line: C:\git\abcl\nbproject\build-impl.xml:980: Java returned: 1 BUILD FAILED (total time: 1 second) On Wed, Jan 16, 2019 at 1:00 PM <armedbear-devel-request(a)common-lisp.net> wrote: > Send armedbear-devel mailing list submissions to > armedbear-devel(a)common-lisp.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://mailman.common-lisp.net/listinfo/armedbear-devel > or, via email, send a message with subject or body 'help' to > armedbear-devel-request(a)common-lisp.net > > You can reach the person managing the list at > armedbear-devel-owner(a)common-lisp.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of armedbear-devel digest..." > > > Today's Topics: > > 1. build failure (Stephen Varey) > 2. Re: build failure (Mark Evenson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 15 Jan 2019 16:14:04 +0100 > From: Stephen Varey <srvarey(a)gmail.com> > To: armedbear-devel(a)common-lisp.net > Subject: build failure > Message-ID: > < > CAMkLg7taP0nVFiAYL7pfKpdObj6r26xzUHU48BhfHOySQbA4rQ(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi > > I downloaded the source and built in netbeans where i get this error > > JAVA-EXCEPTION: Java exception 'java.lang.NoSuchMethodException: No > applicable method named getURLs found in java.lang.ClassLoader or > jdk.internal.loader.ClassLoaders$AppClassLoader'. > C:\git\abcl\etc\ant\netbeans-build.xml:15: The following error occurred > while executing this line: > C:\git\abcl\build.xml:280: The following error occurred while executing > this line: > C:\git\abcl\build.xml:299: Java returned: -1 > BUILD FAILED (total time: 13 seconds) > > Can you help? > > Thanks > stephen >

1 0

build failure
by Stephen Varey 16 Jan '19

16 Jan '19

Hi I downloaded the source and built in netbeans where i get this error JAVA-EXCEPTION: Java exception 'java.lang.NoSuchMethodException: No applicable method named getURLs found in java.lang.ClassLoader or jdk.internal.loader.ClassLoaders$AppClassLoader'. C:\git\abcl\etc\ant\netbeans-build.xml:15: The following error occurred while executing this line: C:\git\abcl\build.xml:280: The following error occurred while executing this line: C:\git\abcl\build.xml:299: Java returned: -1 BUILD FAILED (total time: 13 seconds) Can you help? Thanks stephen

2 1

[Reminder CfP] ELS 2019, 12th European Lisp Symposium, April 1-2, Genova
by Didier Verna 12 Jan '19

12 Jan '19

ELS'19 - 12th European Lisp Symposium Hotel Bristol Palace Genova, Italy April 1-2 2019 In cooperation with: ACM SIGPLAN In co-location with <Programming> 2019 Sponsored by EPITA http://www.european-lisp-symposium.org/ Recent news: - Keynote by Stefan Monnier on Emacs Lisp - Keynote by Christophe Rhodes on SBCL - Guest appearance by Matthew Flatt on Racket The purpose of the European Lisp Symposium is to provide a forum for the discussion and dissemination of all aspects of design, implementation and application of any of the Lisp and Lisp-inspired dialects, including Common Lisp, Scheme, Emacs Lisp, AutoLisp, ISLISP, Dylan, Clojure, ACL2, ECMAScript, Racket, SKILL, Hop and so on. We encourage everyone interested in Lisp to participate. The 12th European Lisp Symposium invites high quality papers about novel research results, insights and lessons learned from practical applications and educational perspectives. We also encourage submissions about known ideas as long as they are presented in a new setting and/or in a highly elegant way. Topics include but are not limited to: - Context-, aspect-, domain-oriented and generative programming - Macro-, reflective-, meta- and/or rule-based development approaches - Language design and implementation - Language integration, inter-operation and deployment - Development methodologies, support and environments - Educational approaches and perspectives - Experience reports and case studies We invite submissions in the following forms: Papers: Technical papers of up to 8 pages that describe original results or explain known ideas in new and elegant ways. Demonstrations: Abstracts of up to 2 pages for demonstrations of tools, libraries, and applications. Tutorials: Abstracts of up to 4 pages for in-depth presentations about topics of special interest for at least 90 minutes and up to 180 minutes. The symposium will also provide slots for lightning talks, to be registered on-site every day. All submissions should be formatted following the ACM SIGS guidelines and include ACM Computing Classification System 2012 concepts and terms. Submissions should be uploaded to Easy Chair, at the following address: https://www.easychair.org/conferences/?conf=els2019 Note: to help us with the review process please indicate the type of submission by entering either "paper", "demo", or "tutorial" in the Keywords field. Important dates: - 01 Feb 2019 Submission deadline - 01 Mar 2019 Notification of acceptance - 18 Mar 2019 Final papers due - 01-02 Apr 2019 Symposium Programme chair: Nicolas Neuss, FAU Erlangen-Nürnberg, Germany Programme committee: Marco Antoniotti, Universita Milano Bicocca, Italy Marc Battyani, FractalConcept, France Pascal Costanza, IMEC, ExaScience Life Lab, Leuven, Belgium Leonie Dreschler-Fischer, University of Hamburg, Germany R. Matthew Emerson, thoughtstuff LLC, USA Marco Heisig, FAU, Erlangen-Nuremberg, Germany Charlotte Herzeel, IMEC, ExaScience Life Lab, Leuven, Belgium Pierre R. Mai, PMSF IT Consulting, Germany Breanndán Ó Nualláin, University of Amsterdam, Netherlands François-René Rideau, Google, USA Alberto Riva, Unversity of Florida, USA Alessio Stalla, ManyDesigns Srl, Italy Patrick Krusenotto, Deutsche Welle, Germany Philipp Marek, Austria Sacha Chua, Living an Awesome Life, Canada Search Keywords: #els2019, ELS 2019, ELS '19, European Lisp Symposium 2019, European Lisp Symposium '19, 12th ELS, 12th European Lisp Symposium, European Lisp Conference 2019, European Lisp Conference '19 -- Resistance is futile. You will be jazzimilated. Lisp, Jazz, Aïkido: http://www.didierverna.info

1 0

← Newer
1
...
9
10
11
12
13
14
15
...
121
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-devel