Re: Trouble running abcl 1.5.0 with java 1.8.0_161 on macOS 10.12.6

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