On Jun 9, 2018, at 16:48, Carlo Tambuatco <oraclmaster@gmail.com> wrote:

It seems to build fine, and generate the abcl.jar in the dist/ folder when I build from source.

But this error occurs when I run the generated abcl wrapper:

Armed Bear Common Lisp 1.5.0 Java 1.8.0_161 Oracle Corporation Java HotSpot(TM) 64-Bit Server VM Low-level initialization completed in 0.282 seconds. org.armedbear.lisp.IntegrityError

[…]

ERROR placeholder called with arguments: Failed to find loadable system file 'autoloads-gen' in boot classpath. Failed to find loadable system file 'autoloads-gen' in boot classpath.

[…]

It seems to recognize the correct java to build from, but I have no idea what these integrity errors mean.

This error means that ABCL cannot locate the "org/armedbear/lisp/autoloads-gen.abcl” file, which should exist within the “abcl.jar” file if your build really has succeeded, and you really are using this file from the generated abcl wrapper. In order to statup quicker, ABCL does not automatically load all its code into memory, but instead uses a mechanism by which functionality is loaded as it is referenced. The “autoload-gen.abcl” file contains the instructions for these autoload sequences, generated at build time. Either your “abcl.jar” is incomplete and lacks this file because your build process failed, or you aren’t invoking ABCL in the way you think you are. I would recommend performing a clean build by invoking “ant clean” before running the mainbuild, afterwards examining closely the end of the build log to ensure that the autogen sequence executes correctly. Then I would simply try to invoke ABCL via “java -jar abcl.jar” from the “dist/“ directory to diagnose any problems you have with invocation. Given that you seem to be same person who recently reported problems to MacPorts building ABCL with JDK8, JDK9 and JDK10 installed, I bet that your problems stem from somehow invoking an incompatible java and/or javac sometime during the build/run process. I would ensure that the both the java/javac executables in your PATH and the JAVA_HOME environment variables reference JDK8. -- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now."

On 2018-06-09 16:48, Carlo Tambuatco wrote:

It seems to build fine, and generate the abcl.jar in the dist/ folder when I build from source.

But this error occurs when I run the generated abcl wrapper:

Armed Bear Common Lisp 1.5.0 Java 1.8.0_161 Oracle Corporation Java HotSpot(TM) 64-Bit Server VM Low-level initialization completed in 0.282 seconds. 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.Load$load_system_file.execute(Load.java:763) at org.armedbear.lisp.LispThread.execute(LispThread.java:814) at org.armedbear.lisp.Lisp.evalCall(Lisp.java:575) at org.armedbear.lisp.Lisp.eval(Lisp.java:540) at org.armedbear.lisp.Load.loadStream(Load.java:629) at org.armedbear.lisp.Load.loadFileFromStream(Load.java:597) at org.armedbear.lisp.Load.loadFileFromStream(Load.java:477) at org.armedbear.lisp.Load.loadSystemFile(Load.java:375) at org.armedbear.lisp.Interpreter.initializeLisp(Interpreter.java:172) at org.armedbear.lisp.Interpreter.createDefaultInstance(Interpreter.java:102) at org.armedbear.lisp.Main$1.run(Main.java:46) at java.lang.Thread.run(Thread.java:748) ERROR placeholder called with arguments: Failed to find loadable system file 'autoloads-gen' in boot classpath. Failed to find loadable system file 'autoloads-gen' in boot classpath. Exception in thread "interpreter" 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.Load$load_system_file.execute(Load.java:763) at org.armedbear.lisp.LispThread.execute(LispThread.java:814) at org.armedbear.lisp.Lisp.evalCall(Lisp.java:575) at org.armedbear.lisp.Lisp.eval(Lisp.java:540) at org.armedbear.lisp.Load.loadStream(Load.java:629) at org.armedbear.lisp.Load.loadFileFromStream(Load.java:597) at org.armedbear.lisp.Load.loadFileFromStream(Load.java:477) at org.armedbear.lisp.Load.loadSystemFile(Load.java:375) at org.armedbear.lisp.Interpreter.initializeLisp(Interpreter.java:172) at org.armedbear.lisp.Interpreter.createDefaultInstance(Interpreter.java:102) at org.armedbear.lisp.Main$1.run(Main.java:46) at java.lang.Thread.run(Thread.java:748)

It seems to recognize the correct java to build from, but I have no idea what these integrity errors mean.

That happened to me too, when building on Linux (using Ubuntu 16.04.3, ant 1.9.6 and openjdk 1.8.0_131 at that time).  A build on Windows 10 x86_64 using IntelliJ 2016.3.4 ) using the sources from the same zip file did succeed however. I noticed that the files in the zip archive are DOS formatted, which _shouldn't_ cause any such issue (making comparison with the files in the git repository a bit more cumbersome though).  I haven't investigated this further, as I got now a working abcl by cloning the git repository and the HEAD as well as a branch off of commit 3e92245341ef07dd0915d1f7f59fa335626330db (release 1.5 [a tag would be nice, imho]) build and run successful, as far as I can tell. hth ~ Günther