Paul Cochrane wrote:
Sorry, I guess there was some mental PATH overloading going on. Try adding the absolute path to F<blib/lib> to PATH.export PATH=/path/to/parrot/blib/lib:$PATH And then "make."I tried this (although, I appended the blib path to PATH, not sure if that makes a difference) and parrot builds, but it fails a whole heap of tests, and gets to t/src/io.t and eventually runs out of memory. Attached is the 'make test' output of parrot from r17829.
The first libparrot.dll in PATH is used, so unless you've got an installed Parrot it shouldn't matter.
I'm getting the same test results. That's the current state of Parrot on Cygwin. See http://smoke.parrotcode/org/smoke section i386-cygwin-gcc.
Actually, you can't smoke parrot without user intervention. F<t/src/io.t> seems to consume an infinite amount of memory, or at least tries to. Haven't look into the details yet, but I think one test creates an executable io_4.exe which doesn't stop printing results, which cause the out of memory situation. I usually just kill io_4.exe. (I know, that's a bad thing, but that's what bad people do.)
Not 100% on this, but I think one or two of the stm tests hang, too. Ron
