On Thu, Oct 25, 2012 at 3:16 AM, Ralph Möritz <ralph.moeritz@outlook.com> wrote:
> On Wed, Oct 24, 2012 at 10:24 AM, Ralph Möritz 
> <ralph.moeritz@outlook.com<mailto:ralph.moeritz@outlook.com>> wrote:
> I just downloaded MKCL-1.1.0 & tried compiling a small "Hello, world"
> program on Windows without success. Here's what I tried:
>
> 1. Add "C:\Program Files\MKCL 1.1\bin" to my PATH.
> 2. Run `mkcl -not-fasl-p -compile hello.lisp` which produces lisp.o
> 3. Now what? I've tried to link using `gcc -o hello.exe hello.o
> -lmkcl_1.1.0` which produces an error:
>
> Such a direct call to gcc cannot work with a ".o" produced by the MKCL
> compiler (see [1] below as to why). 

Ah! Thanks for elaborating.

Yes I know, this should be clearly explained in the documentation...
 

...
In my spare time I'm writing a chess engine. Chess engines are usually provided
to users as statically linked native executables. Of course I'm using SLIME 
interactively during development, but I'd like to be able to build the executable from the 
command-line as well. Normally I use SBCL, but I'm experimenting with ECL & MKCL specifically 
to be able to produce native executables from my Lisp code.


Well, in that case all I can add is: Thank you very much for the bug report and I am working on a fix right now.