Jerry Gay (via RT) ha scritto:
i suspect there's trouble with the platform-specific c/h files, given the nature of the warnings during build. the configure/make output is below.
the only relevant warning I see is:
config/gen/platform/win32/exec.c: In function `Parrot_Exec_OS_Command': config/gen/platform/win32/exec.c:182: warning: passing arg 2 of `_execvp' from i ncompatible pointer type
this seems to be generated by the difference between 'char **' and 'char* const*'. I don't think this is a great problem.
Invoking Parrot to generate runtime/parrot/include/config.fpmc --cross your fing ers ./miniparrot.exe config_lib.pasm > runtime/parrot/include/config.fpmc '.' is not recognized as an internal or external command, operable program or batch file. make: *** [runtime/parrot/include/config.fpmc] Error 1
these last lines seem to suggest that miniparrot.exe was in fact built. the problem, I think, is that make is trying to call miniparrot prepending './', which is sh-style and does not work under Windows CMD. you may have better luck running make from a cygwin shell.
or perhaps you could try mingw32-make instead of make as Configure.pl suggests?
on the other hand, I had a totally different experience using strawberry perl to build parrot. it doesn't work at all, make groks because of backslashes in paths in the Makefile (had to change them to forward slashes), libparrot.dll refuses to build because, apparently, g++ is unable to link correctly (it says: "cc1.exe \: no such file or directory"). YMMV.
cheers, Aldo
