armedbear / abcl

Armed Bear Common Lisp <git+https://github.com/armedbear/abcl/> <--> <svn+https://abcl.org/svn> Bridge
https://abcl.org#rdfs:seeAlso<https://gitlab.common-lisp.net/abcl/abcl>
Other
289 stars 29 forks source link

Loading abcl on Raspberry Pi #359

Open Slids opened 3 years ago

Slids commented 3 years ago

Built from head on Raspbian

./common-lisp/abcl/abcl Armed Bear Common Lisp 1.8.1-dev Java 1.8.0_40-internal Oracle Corporation OpenJDK Zero VM Low-level initialization completed in 3.864 seconds. Startup completed in 54.163 seconds. (print 'a) WARNING: You are using ASDF version 3.3.4.0.1 (probably from (require "asdf") or loaded by quicklisp) and have an older version of ASDF 3.1.4 registered at #P"/usr/share/common-lisp/source/cl-asdf/asdf.asd". Having an ASDF installed and registered is the normal way of configuring ASDF to upgrade itself, and having an old version registered is a configuration error. ASDF will ignore this configured system rather than downgrade itself. In the future, you may want to either: (a) upgrade this configured ASDF to a newer version, (b) install a newer ASDF and register it in front of the former in your configuration, or (c) uninstall or unregister this and any other old version of ASDF from your configuration. Note that the older ASDF might be registered implicitly through configuration inherited from your system installation, in which case you might have to specify :ignore-inherited-configuration in your in your ~/.config/common-lisp/source-registry.conf or other source-registry configuration file, environment variable or lisp parameter. Indeed, a likely offender is an obsolete version of the cl-asdf debian or ubuntu package, that you might want to upgrade (if a recent enough version is available) or else remove altogether (since most implementations ship with a recent asdf); if you lack the system administration rights to upgrade or remove this package, then you might indeed want to either install and register a more recent version, or use :ignore-inherited-configuration to avoid registering the old one. Please consult ASDF documentation and/or experts.

Failed to require JAVA because 'Failed to get InputStream for jar:file:///home/pi/common-lisp/abcl/dist/abcl.jar!/org/armedbear/lisp/java' Failed to require KNOWN-SYMBOLS because 'Don't know how to REQUIRE JAVA.' Error loading jar:file:///home/pi/common-lisp/abcl/dist/abcl.jar!/org/armedbear/lisp/compiler-pass2.abcl at line 15 (offset 951)

<THREAD "interpreter" {EA9DF1}>: Debugger invoked on condition of type SIMPLE-ERROR

Don't know how to REQUIRE KNOWN-SYMBOLS. Restarts: 0: RETRY Retry ASDF operation. 1: CLEAR-CONFIGURATION-AND-RETRY Retry ASDF operation after resetting the configuration. [1] JVM(1): (ql:quickload :cl-protobufs)

easye commented 3 years ago

OpenJDK Zero is more than a decade old, and probably barely on par with openjdk6 from looking at the release notes.

https://icedtea.classpath.org/wiki/ZeroSharkFaq

Unless there is some other platform constraint that you have, I would try a more contemporary openjdk11 port before trying to debug running on that JDK much further (see for examplehttps://linuxize.com/post/install-java-on-raspberry-pi/).

I certainly had the Bear running on an RPI device early in 2016, so I know it should be possible.