On 3/16/2015 4:07 PM, Achim Gratz wrote:
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
On 3/16/2015 3:41 PM, 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
Yaakov Selkowitz writes:
Looking at the executable it seems that it is a very small (~66 kiB)
stub that then proceeds to load the rest of the file after having
started the runtime. The memory image seems simply bolted on (as an
overlay?), and gets removed when the executable is stripped.
UPX
Ken Brown writes:
The clisp executables are not stripped because apparently there's a
disassemble command within clisp that doesn't work if the executables
are stripped. I don't actually know anything about this, but there
was a comment about that in the .cygport file that I inherited from
On Mon, 2015-03-16 at 23:16 +0100, Achim Gratz wrote:
Ken Brown writes:
The clisp executables are not stripped because apparently there's a
disassemble command within clisp that doesn't work if the executables
are stripped. I don't actually know anything about this, but there
was a
Ken Brown writes:
No it doesn't. Specifically, it doesn't like being stripped. I'll
RESTRICT that, let's hope it works now… Yup, it does.
Great. Thanks for testing. There's probably no reason for me to
upload a new clisp package right now (unless it would help you). But
I'll give you a
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
Achim Gratz writes:
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
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
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
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
On Mar 14 21:30, Achim Gratz wrote:
Corinna Vinschen writes:
So the binutils problem is fixed upstream, we're just waiting for GDB
to catch up. Another collegue of mine will have a look as soon as time
permits.
Here's one for testing, Achim:
12 matches
Mail list logo
