On Wednesday 07 March 2007 08:42, Aldo Calpini wrote: > 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.
Our configuration process tends to assume a tight connection between the operating system and a specific compiler, for example. -- c
