Maybe this strange behavior of C6pre on MSYS2 * is a consequence of what Felix said before: " Make sure you update to the newest CHICKEN 6 version from git. We made some user-visible changes to the process API from (chicken process) and CRUNCH uses this API. " from the CRUNCH testing mail branch?
PS. strange behavior of the C6pre on my windows laptop: 1) When I import my separate module .so into my main.scm and compile just by csc6 main.scm, resulted process 'main' silently ends after start. 2) I cannot build a static module version, the compiler barks when it makes an object file of a module. 3) But I can make a static one-file executable. 4) Which way slower ~10x runs on msys, against the linux version. PPS. Windows OS is not super comfortable, side note. вс, 22 июн. 2025 г. в 12:35, Anton Idukov <[email protected]>: > make check .... Error 127. This is [MSYS2 UCRT64 environment]. For > note, good old chicken-5.4.0 not even built on this msys2 > > вс, 22 июн. 2025 г., 11:27 <[email protected]>: > >> > Hi! On my linux Wine is not installs msys (process sits in memory with >> 99% >> > cpu), so I unpack fresh chip laptop with latest win11 and install MSYS2 >> and >> > next install gcc and git, what's the next steps? (I develop some c >> code on >> > windows about 4 years ago) >> >> You'll need w64devkit (see the CHICKEN README for information) and >> a distribution tarball with the newest changes, which can be found here: >> >> >> http://www.call-with-current-continuation.org/chicken-6-prelim.tar.gz >> >> If you unpack the archive and build it, you will get a "chicken.exe" >> binary that you can then use to bootstrap the system from the >> git sources. If you then run "make check" you will quickly run into >> errors and can then continue to investigate. >> >> Your help is much appreciated! Please ask, if there are any questions. >> >> >> felix >> >>
