Re: [Chicken-users] building under windows

[Răzvan Rotaru]

Hi,

I tried to build from the release tarball 4.8.0 (http://code.call-cc.org/releases/4.8.0/chicken-4.8.0.tar.gz). The command run was:

D:\kit\chicken-4.8.0>mingw32-make PLATFORM=mingw PREFIX=d:/programs/chicken > stderr.txt
process_begin: CreateProcess(NULL, chicken.exe .\build-version.scm -optimize-level 2 -include-path . -include-path ". -i
nline" -ignore-repository -feature chicken-bootstrap -no-warnings -specialize -types .\types.db -explicit-use -no-trace
-output-file build-version.c, ...) failed.
make (e=2): The system cannot find the file specified.
mingw32-make[1]: *** [build-version.c] Error 2
mingw32-make: *** [all] Error 2

Attached you can also find stdout.txt.

Răzvan

On 5 November 2012 22:01, Peter Bex <address@hidden> wrote:

On Mon, Nov 05, 2012 at 09:52:49PM +0100, Răzvan Rotaru wrote:
> Hi,

Hi Răzvan,

> I'm currently trying to build chicken for windows, and am stuck in the
> following step:
>

> GNUmakefile:60: recipe for target 'boot-chicken' failed
> mingw32-make: *** [boot-chicken] Error 2
>
> It seems like I need to have chicken.exe. Can't I compile it without
> bootstrapping?

We'd need some more information on exactly what you did.

Are you building from git?  If so, check out the README file.
It explains how to build Chicken from git.  Basically the idea
is that you first use a release or snapshot tarball to create
a working Chicken and then use that to build from git.

If you get this from a release tarball, something else is wrong.

Cheers,
Peter
--
http://sjamaan.ath.cx
--
"The process of preparing programs for a digital computer
 is especially attractive, not only because it can be economically
 and scientifically rewarding, but also because it can be an aesthetic
 experience much like composing poetry or music."
                                                        -- Donald Knuth

stdout.txt
Description: Text document