This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: Question about clisp version naming
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 16 Mar 2015 20:04:04 +0100
- Subject: Re: Question about clisp version naming
- Authentication-results: sourceware.org; auth=none
- References: <5500B536 dot 4050108 at cornell dot edu> <87bnju6wox dot fsf at Rainer dot invalid> <5505C36F dot 5030802 at cornell dot edu> <1426443595 dot 8104 dot 9 dot camel at cygwin dot com> <5505D57C dot 3040005 at cornell dot edu> <87twxm5azp dot fsf at Rainer dot invalid> <55060BF6 dot 80801 at cornell dot edu>
Ken Brown writes:
> Just for testing purposes, I've built a new clisp with
> /usr/bin/cyglisp.dll and /usr/lib/liblisp.dll.a, and I've uploaded it
> to my Cygwin repository:
>
> http://sanibeltranquility.com/cygwin/
>
> When you get a chance, please test it and see if it allows you to
> avoid your workaround. If so, I'll think about whether it's worth
> repackaging following Fedora.
This has the same problem as the current release: any attempt to run
lisp.exe (or an executable dump) will produce this message:
...lib/clisp-2.49+/base (2120) ./lisp.exe
module 'syscalls' requires package OS.
/mnt/share/maint (2125) /usr/lib/clisp-2.49+/base/lisp.exe
module 'syscalls' requires package OS.
The loading of memory images via clisp works, so I'll pull the
maxima-exec-clisp package until we get to the bottom of this.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
DIY Stuff:
http://Synth.Stromeko.net/DIY.html