On 12/23/05, Peter Schwenn <[EMAIL PROTECTED]> wrote: > Dear 6Compilers, > questions about the internals of parrot (including build/config trouble) are best directed instead to the perl6 internals list, so i've copied them on my response.
> Cygwin isn't entirely happy with Parrot (don't know about Pugs). Is the > best approach on "plain" windows for setting up perl5+pugs+parrot to: > > 1. set up a gcc environment > 2. get the ....tar.gz sources involved > 3. use gcc's make to make, make test, make install each of > perl (587? or 592?), pugs and parrot > (4. CPANPLUS, ...) > cygwin *should* compile parrot just fine. the last report i see on http://smoke.parrotcode.org/smoke/ for i386-cygwin-gcc is from r10487, which is a few weeks old, though. can any other cygwin users confirm peter's report? there have been some significant changes to the config system lately, these may have broken your platform. i don't understand what you mean by "plain" windows. i use windows with msvc 6 & 7.1. others use msys with mingw. we consider cygwin a different platform, so it's not really "windows" at all. > OR > > is there an advantageous alternative involving PXPerl or ... or some > Cygwin alternative or ...? > i mentioned msys with mingw, which is an alternative. also, there are free microsoft compiler tools, which have been tested in the past, however the only recent reports i know of these are from a ppc-osx emulating i386-windows running them, where the build failed. that's a rather hard setup to debug, though. there should be a good bit of useful information in README.win32, in the parrot root directory. > OR > > work to make Cygwin work (e.g. to Configure.pl Parrot's Makefile) > if it's failing in cygwin, this is the best fix. > PeterS > thanks for reporting. if you can provide the specifics of the config failure and your platform information, this would be much appreciated. ~jerry
