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 21:07:31 +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> <1426535835 dot 8104 dot 62 dot camel at cygwin dot com>
Yaakov Selkowitz writes:
> Is there an issue with stripping clisp executables?
Yes, with the executable dumps.
> Is there a magic
> number we can use to detect these automatically?
File identifies them as plain executables. CLisp knows which runtime
they were rpdocued from, so there must by some symbols to pull this
information from. Ken should have an answer, otherwise I can
investigate later. In any case these are the only executables shipped
with maxima, so RESTRICT=strip doesn't do any harm at the moment.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada