Hi,

I tried to touch build-version.c but with no change. I would have been
surprised to see one, since all other .c file have the same timestamp.

I commented out the lines 556-558 from rules.make and succeeded with the
build. To me it looks like a bug in make.

For your information, I tried to use the toolchains provided by
http://www.mingw.org and http://mingw-w64.sourceforge.net. Both have the
same behaviour. (allthough the second one displayed some warnings, which
were not displayed by the first one).

Răzvan


On 6 November 2012 21:00, Felix <[email protected]>wrote:

> From: Răzvan Rotaru <[email protected]>
> Subject: Re: [Chicken-users] building under windows
> Date: Tue, 6 Nov 2012 10:27:58 +0100
>
> > 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.
>
> Hi!
>
> Try to "touch" build-version.c - you can simply open it with
> an editor and add a space somewhere (i.e. just modify and save
> it to update the timestamp).
>
>
> cheers,
> felix
>
_______________________________________________
Chicken-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/chicken-users

Reply via email to