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 somewhere, but I didn't find the URL.
I got something not so far from my needs with chicken-iup prebuilt files and a small batch script which override CHICKEN_INSTALL_PREFIX and CHICKEN_PREFIX. Now I would like to compile Chicken from sources for Windows 32 and 64 bits. > Perhaps this has something to do with mingw32-64. Did you read the README > instructions to invoke mingw32-make with "ARCH=x86-64" and use forward > slashes in all paths? If not, does that help? If it doesn't help, is it > at all possible to do a 32-bit build on 64-bit Windows? If I don't add the option "ARCH=x86-64" the compilation phase fails when compiling ASM instructions for apply-hack function. I guess x64 ASM have a different instruction set from 32 bits. >From what I understand, there is no way to cross-compile for Windows 32 bits >from a 64 bits host with ming32-64. If you use "ARCH=x86-64" it means both HOST and TARGET are 64 bits. Did you use mingw 32 bits? Which version? I would like to try on my side. Actually I did read the README, but I didn't follow all the instructions: - I didn't set PREFIX, coming from Linux world, I expect it to be the current directory by default - Since I override 2 variables at execution level, it should have no issue Anyway, I have just tried again to compile with an absolute PREFIX including drive letter and normal slash "/". The issue remains. I tried with the 2 compilers. Honestly, I don't understand the needs to have an absolute PREFIX. In the common cases, when you want to use unix tools on Windows, you just have to override the PATH locally with batch script. Can you confirm the PREFIX is not mandatory and can be overridden by environment variables at execution level? Regards, Pascal ----- Mail original ----- De: "Peter Bex" <peter....@xs4all.nl> À: comb...@laposte.net Cc: chicken-users@nongnu.org Envoyé: Lundi 1 Décembre 2014 23:15:26 Objet: Re: [Chicken-users] Strange behavior of Chicken Scheme interpreter on Windows 7 On Mon, Dec 01, 2014 at 03:40:10PM +0100, comb...@laposte.net wrote: > Hi everybody, Hello and welcome to CHICKEN! > 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" > - the current version, build date and additional information is displayed in > the SAME terminal > - the REPL let write Scheme program in the SAME terminal This is what should happen. > Observed behavior: > - open cmd.exe and cd to the build directory > - type "csi" > - A new window is opened (looks like a cmd.exe terminal), the current > version, build date and additional information is displayed in this window > - (wait around 15 seconds) > - The new window is automatically closed (!) and all the output of the closed > window in redirected in the original terminal This definitely should not happen. > This behavior does not appears in the prebuilt binaries of chicken-iup (32 > bits). > > 2 questions: > - This behavior is it normal? Can it be explained? It is definitely not normal, and I can't explain it. I've never seen this happen, and I've built CHICKEN on Windows quite a few times already. > - How to avoid this behavior? Without knowing why it happens, I'm afraid I can't tell you how to avoid it. > Conditions: > - Windows 7 64-bits, Intel > - Compiled from sources with Mingw (tried with mingw32-64 SJLC, mingw32-64 > FEH) > - Chicken Scheme 4.9.0.1 (also tried with chicken-4.6.3, chicken-4.8.0.5, > chicken-4.8.1) > - With the makefile.mingw and makefile.mingw-MSYS (msys binaries of 2011) Perhaps this has something to do with mingw32-64. Did you read the README instructions to invoke mingw32-make with "ARCH=x86-64" and use forward slashes in all paths? If not, does that help? If it doesn't help, is it at all possible to do a 32-bit build on 64-bit Windows? Cheers, Peter -- http://www.more-magic.net
_______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
