Anteusz @ Freemail . Hu <[EMAIL PROTECTED]> wrote:
> I found two bugs while trying to compile 0.1.2
Parrot is developing rapidly, please use always the CVS version for
submitting bugs and patches.
But as this one ...
> I added o => '.o'.
... is still the same - no problem here.
Strange anyway. Folks reported that MinGW builds Parrot 0.1.2 ok.
What setting for 'o' is correct?
> The second bug is:
> I have windows xp, mingw 3.2.3, icu 2.8 v6 , activestate perl 5.6
> my method:
> set path=%path%;c:\mingw3\bin;D:\extracted\icu\icu\bin
> d:
> cd D:\extracted\parrot-0.1.2
> perl configure.pl --cc=gcc --cxx=gcc --link=gcc --libs=""
> --linkflags=-machine:x86 --ccflags="-O1 -MD -DNDEBUG -DWIN32 -D_CONSOLE
^^^
This might have caused the problem. Can you try to build an unoptimized
version please.
> ops/experimental.ops: In function `switch_core':
> ops/experimental.ops:263: unable to find a register to spill in class
> `DIREG'
But in the long run, we have to get rid of a lot of opcodes. This is
just another example where compilers don't grok core_ops*.c any more.
leo
