This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: Question about clisp version naming
- From: Yaakov Selkowitz <yselkowitz at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 16 Mar 2015 14:57:15 -0500
- 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>
On Mon, 2015-03-16 at 20:41 +0100, Achim Gratz wrote:
> Achim Gratz writes:
> >> 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.
> >
> > Hmm. Scratch that, I think I got the maxima.exe (dumped image) to work.
> > Let's see if it survives installation.
>
> No it doesn't. Specifically, it doesn't like being stripped. I'll
> RESTRICT that, let's hope it works nowâ Yup, it does.
Ken, Achim,
Is there an issue with stripping clisp executables? Is there a magic
number we can use to detect these automatically?
--
Yaakov