Hi,
You are right, apply-hack.x86-64.S looks to be disabled. I didn't notice
before.
Does it mean that Windows 64 bits is not fully supported?
I tried to add Apply-hack.x86-64.S in the build, but it does not compile
correctly.
Strange, the syntax of the gcc assembly is different from
Hello,
I made some build of chicken on 64 bits and 32 bits.
Basically, the system looks to work correctly: i tried some random packages,
for example win32-msgbox works correctly.
A few other packages also works out-of-the-box, you have made a good job!
I would like to use slime with Emacs
Peter,
I found the root cause of my issue, it is not related to Chicken Scheme, it's
pretty simple.
Actually, it took me a long time to realize there is some kind of sandboxing
mechanisms in avast! antivirus.
It redirect the input/output to some temporary window during the scanning of
the
Thank you for your fast answer :)
My target is to have a standalone archive file (including Chicken + GCC) that I
can copy on my USB key and use on different computers.
Usage: portable Chicken scheme development environment for Windows without
admin privileges.
It probably already exist
Hi everybody,
My problem is not really an issue, since the scheme interpreter is working
correctly in my test conditions.
But I noticed a strange behavior on Chicken interpreter with my 4.9.0.1 build
of Chicken.
Expected behavior:
- open cmd.exe and cd to the build directory
- type csi
-