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 binary file.
> That doesn't make sense. PREFIX is *never* the current directory on
> Linux. The PREFIX is where you are going to _install_ the program, not
> where you're compiling it.
I made a mistake when writing the sentence.
I now understand there is a big difference between the behavior on Windows and Linux.
On Linux PREFIX is an option, you can decide to set it, but the default location is a valid directory.
Now I am a little bit confused by your answer.
1. PREFIX looks to be mandatory in Chicken and is an absolute path
2. I want to package everything in an archive file which will be in different places on different computers
De: "Peter Bex" <address@hidden>
À: address@hidden
Cc: address@hidden
Envoyé: Jeudi 4 Décembre 2014 16:00:26
Objet: Re: [Chicken-users] Strange behavior of Chicken Scheme interpreter on Windows 7
On Tue, Dec 02, 2014 at 03:20:05PM +0100, address@hidden wrote:
> 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'm not aware of anything like that.
> 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.
Cool.
> > 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.
Yes, that's what ARCH is for. I thought you were trying to build a
64 bit binary, hence my suggestion.
> 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.
I don't think there's a Windows-to-Windows cross build.
> Did you use mingw 32 bits? Which version? I would like to try on my side.
Yeah, I used the 32-bits mingw. I generally just download the latest
from the website.
> 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
That doesn't make sense. PREFIX is *never* the current directory on
Linux. The PREFIX is where you are going to _install_ the program, not
where you're compiling it.
> - 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.
Did you set PREFIX to the target where you are going to install it, or to
the directory where the CHICKEN sources are? If the latter, that's
probably what's going wrong.
> 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?
No, PREFIX is required and I think it really must be an absolute path.
Cheers,
Peter
--
http://www.more-magic.net