note on clisp on windows

[Qian Yun]

1. Just as the documentation says, clisp does not support
building from source natively on 64 bit windows.

https://gitlab.com/gnu-clisp/clisp/-/blob/master/INSTALL.windows?ref_type=heads

2. But mingw-w64 is dropping 32bit support for its dependency
ffcall, libsigsegv.

3. The clisp-2.49 binary can run on windows 10, but not on
windows 11 when "load" a file. It reports this error:

Win32 error 267 (ERROR_DIRECTORY): The directory name is invalid

Probably due to an obsolete way in file operation.
(LLM says it is related with insecure relative path resolution.)
And it doesn't look being fixed in git HEAD.


Sadly, it looks like clisp is slipping into abandonware.

- Qian

[Qian Yun]

On 8/9/26 1:27 PM, Qian Yun wrote:
> 1. Just as the documentation says, clisp does not support
> building from source natively on 64 bit windows.
>
> https://gitlab.com/gnu-clisp/clisp/-/blob/master/INSTALL.windows?ref_type=heads
>
> 2. But mingw-w64 is dropping 32bit support for its dependency
> ffcall, libsigsegv.
>
> 3. The clisp-2.49 binary can run on windows 10, but not on
> windows 11 when "load" a file. It reports this error:
>
> Win32 error 267 (ERROR_DIRECTORY): The directory name is invalid

Aha! Just find out this:
https://gitlab.com/gnu-clisp/clisp/-/merge_requests/14

Should fix it. Not tried though.

(I will try to build a new 32bit clisp binary when the
github windows-2022 runner is retired. That should
happen in 2 years. If no one beats me to it...)

- Qian