I have found a buildversion.c file in the tarball, in the root folder where the makefiles are. Looks like the mingw make behaves different...
On 6 November 2012 14:01, Peter Bex <[email protected]> wrote: > On Tue, Nov 06, 2012 at 10:27:58AM +0100, Răzvan Rotaru wrote: > > 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. > > This looks like it's attempting to build build-version.c from > build-version.scm > > I checked the tarball, but it contains the build-version.c file. > Can you double check it's in your file too? Did you run any > extra commands before the one above? > > 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 >
_______________________________________________ Chicken-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-users
