Re: armedbear-devel Digest, Vol 64, Issue 4

I have also tried powerloom with Allegro common lisp which works fine.
It works with LispWorks if you change one option to do with a the latin-1
char set.


On Wed, May 20, 2020 at 2:00 PM <[email protected]>
wrote:

> Send armedbear-devel mailing list submissions to
>         [email protected]
>
> 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
>         [email protected]
>
> You can reach the person managing the list at
>         [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of armedbear-devel digest..."
>
>
> Today's Topics:
>
>    1. Re: help with verify error (Mark Evenson)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 19 May 2020 22:19:00 +0200
> From: Mark Evenson <[email protected]>
> To: abcl-dev <[email protected]>
> Cc: Stephen Varey <[email protected]>
> Subject: Re: help with verify error
> Message-ID: <[email protected]>
> Content-Type: text/plain;       charset=utf-8
>
>
>
> > On May 18, 2020, at 18:42, Stephen Varey <[email protected]> wrote:
> >
> > I am trying to load powerloom into abcl.
> >
> > If you download powerloom (
> https://www.isi.edu/isd/LOOM/PowerLoom/download.html#PowerLoom)
> >
> > start abcl and then (load "~/powerloom-4.0.10/load-powerloom.lisp") ;;;
> assuming downloaded into home directory
> >
> > It fails with the following stacktrace.
> >
> > Can you help?
>
> This code expresses a bug in the compiler.  Due to the ISI codebase doing
> what
> would be considered nowawdays real hacks around compilation, it will take
> a bit
> of effort to isolate the exact problem in the compiler, but it gives a
> practical problem to improve the disassembly tools.
>
> The ISI codebase hasn’t been updated since 2010.  It works under CCL, but
> not
> SBCL so ABCL isn’t the only implementation with problems here.
>
> I’ve filed [an issue][186][467].
>
> [186]: https://github.com/armedbear/abcl/issues/186
> [467]: https://abcl.org/trac/ticket/467
>
> Thanks for trying out the Bear; we’ll see what we can do to get your code
> running, as it is a great example of a substantial application.
>
> >
> > STELLA 3.5.35 loaded.
> > Type `(in-package "STELLA")' to execute STELLA commands.Making required
> system logic
> > java.lang.VerifyError: (class: org/armedbear/lisp/pl_kernel_kb_2,
> method: <clinit> signature: ()V) Bad type in putfield/putstatic
> > at java.lang.Class.getDeclaredConstructors0(Native Method)
> > at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671)
> > at java.lang.Class.getConstructor0(Class.java:3075)
> > at java.lang.Class.newInstance(Class.java:412)
> > at
> org.armedbear.lisp.FaslClassLoader.loadFunction(FaslClassLoader.java:130)
> […]
> > at java.lang.Thread.run(Thread.java:745)
> > Error loading
> /home/srv/powerloom-4.0.10/native/lisp/bin/lisp/logic/pl-kernel-kb.sabcl at
> line 44 (offset 3242)
> > #<THREAD "interpreter" {5B983350}>: Debugger invoked on condition of
> type ERROR
> >   Compiled function can't be loaded: org.armedbear.lisp.pl_kernel_kb_2
> from org.armedbear.lisp.Pathname@54789d54
> > Restarts:
> >   0: TOP-LEVEL Return to top level.
> > [1] STELLA(2):
>
> --
> "A screaming comes across the sky.  It has happened before but there is
> nothing
> to compare to it now."
>
>
>
>
>
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> armedbear-devel mailing list
> [email protected]
> https://mailman.common-lisp.net/listinfo/armedbear-devel
>
>
> ------------------------------
>
> End of armedbear-devel Digest, Vol 64, Issue 4
> **********************************************
>