Thanks Peter.
I messed up the threading on this conversation, and went into more details elsewhere about my adventures into getting this working, and I've tried more since.
I've had no luck with the latest version (5.3.0rc2); I discovered (via strace) that the created executable is internally loop crashing under gcc 10.3 mingw64/msys2
Nor were my various attempts to downgrade mingw64 to gcc 10.2 in (mingw64/msys2) successfully, it just failed to compile, but that's probably because downgrading msys2 is difficult as you have to manually try and apply downgraded packages.
I tried compiling via mingw64 for windows (chocolatey instead of msys2), which worked in compilation, but there's an issue with file paths mixing windows and unix slash types.
I then tried the chocolatey chicken package but the maintainer has compiled it with incorrect flags, so the copy phase of eggs is broken (uses "cp -r" instead of windows copy). I'm awaiting to see if that gets fixed (
https://community.chocolatey.org/packages/chicken), but i'm not holding my breath as there's several comments over recent months with the same message (I at least feel I've tried to pinpoint the issue for the maintainer though).
I've tried at least 6 different methods to get chicken working on windows, and they are all sadly broken in some way.
It's an awful state. the docs (
http://wiki.call-cc.org/msys2) still refer to 5.0.0, and it simply doesn't work as written (I'm doing this on clean installations of everything). I suspect gcc versions, but it doesn't feel like anyone owns this, so there's no regular build on windows with latest mingw64/msys2 to check.
And in no way am I trying to start any implementation wars, but after hours of this, in exasperation, I ran racket, and it just worked.
Mark