Re: on cygwin target, executable only starts if named lisp.exe

[Vibhu M. <vi...@ho...>]

On 05/04/2024 02:52, Vibhu Mohindra wrote:
> If anyone makes observations that contradict mine, I'd love to hear, 
> because it means I should start afresh and rationalise my build software 
> versions and configuration options. I'm posting this in case it's a real 
> bug easily reproducible with whatever Cygwin version and configuration 
> flags anyone may use.

I've verified that the problem also occurs on a fresh checkout of clisp 
head, using the latest Cygwin and Cygwin packages, this time with 
libsigsegv libs/headers installed.

./configure build3c64c64
configure results: FFI: yes, readline: no, libsigsegv: yes
build succeeds, out of the box.
loading a saved executable image has the same problem, segfault.

I also notice that Cygwin has a clisp package of its own. That build has a 
patch dated April 2015 applied to refuse to save images if they are to be 
executable. Maybe the patch author noticed the same problem back then that 
I have noticed now.

https://cygwin.com/cgit/cygwin-packages/clisp/tree/cygwin-no-save-executable.patch

Vibhu