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: Wed, 18 Mar 2015 06:33:59 +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> <87k2ygbw7v dot fsf at Rainer dot invalid> <87fv94bveq dot fsf at Rainer dot invalid> <87bnjsbuhm dot fsf at Rainer dot invalid> <55073E93 dot 2030902 at cornell dot edu> <87vbhzph1g dot fsf at Rainer dot invalid> <5508998A dot 6040903 at cornell dot edu> <1426628400 dot 12464 dot 38 dot camel at cygwin dot com> <5508AD6F dot 60309 at cornell dot edu>
Ken Brown writes:
>> How does the
>> lisp.exe in clisp relate to the one that would be in maxima-exec-clisp?
>
> Achim will have to answer this one.
I don't really know either. The executable dump is provided by clisp
and you can name the resulting exe any which way you want. For maxima,
it's maxima.exe. This file is (looking at both the non-executable
memory image and the executable one) an exe stub with the non-executable
image as an overlay. I don't really know where the stub comes from, but
I don't see it directly relating to lisp.exe at the moment.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra